Part II Store and Manage JSON Data
This part covers creating JSON columns in a database table, partitioning such tables, replicating them using Oracle GoldenGate, and character-set encoding of JSON data. It covers the use of SQL/JSON condition is json
as a check constraint to ensure that the data in a column is well-formed JSON data.
- Overview of Storing and Managing JSON Data
This overview describes: (1) data types for JSON columns, (2) LOB storage considerations for JSON data, and (3) ensuring that JSON columns contain well-formed JSON data. - Creating a Table With a JSON Column
You can create a table that has JSON columns. You use SQL conditionis json
as a check constraint to ensure that data inserted into a column is (well-formed) JSON data. Oracle recommends that you always use anis_json
check constraint when you create a column intended for JSON data. - SQL/JSON Conditions IS JSON and IS NOT JSON
SQL/JSON conditionsis json
andis not json
are complementary. They test whether their argument is syntactically correct, that is, well-formed, JSON data. You can use them in aCASE
expression or theWHERE
clause of aSELECT
statement. - Character Sets and Character Encoding for JSON Data
JSON data always uses the Unicode character set. In this respect, JSON data is simpler to use than XML data. This is an important part of the JSON Data Interchange Format (RFC 4627). For JSON data processed by Oracle Database, any needed character-set conversions are performed automatically. - Partitioning JSON Data
You can partition a table using a JSON virtual column as the partitioning key. The virtual column is extracted from a JSON column using SQL/JSON functionjson_value
. - Replication of JSON Data
You can use Oracle GoldenGate to replicate tables that have columns containing JSON data.