Content Column JSON Validation

The script content on this page is for navigation purposes only and does not alter the content in any way.

The collection metadata component that specifies the syntax to which JavaScript Object Notation (JSON) content must conform—strict or lax.

Note: If the content column stores JSON data using Oracle’s native binary format OSON — either JSON type or BLOB with format OSON, then this metadata component is absent.

Property	Value
Default value	STANDARD
Allowed values	STANDARD STRICT LAX (default for SQL condition is json)
JSON collection metadata document path	contentColumn.validation

• STANDARD validates according to the JSON RFC 8259 standard (or the RFC 4627 standard, if database initialization parameter compatible is less than 20). It corresponds to the strict syntax defined for Oracle SQL condition is json.¹

• STRICT is the same as STANDARD, except that it also verifies that the document does not contain duplicate JSON field names. (It corresponds to the strict syntax defined for Oracle SQL condition is json when the SQL keywords WITH UNIQUE KEYS are also used.)

• LAX validates more loosely. (It corresponds to the lax syntax defined for Oracle SQL condition is json.) Some of the relaxations that LAX allows include the following:

  • It does not require JSON field names to be enclosed in double quotation marks (").

  • It allows uppercase, lowercase, and mixed case versions of true, false, and null.

  • Numerals can be represented in additional ways.

See Also:

• Oracle Database JSON Developer’s Guide for information about strict and lax JSON syntax
• IETF RFC 8259 for the JSON RFC 8259 standard
• IETF RFC 4627 for the JSON RFC 4627 standard

Related Topics

• Default Collection Metadata

1. In database releases prior to 20c only IETF RFC 4627 was supported. It allows only a JSON object or array, not a scalar, at the top level of a JSON document. RFC 8259 support includes RFC 4627 support (and RFC 7159 support). ↩