How Designer Gets Data from JSON Data Sources
Using Designer, you can parse JSON data to extract JSON schemas including JSON metadata (JSON objects and the relation between the objects), transform JSON schemas to relational schemas, and build relational tables during the transformation, namely map JSON object classes to tables and table columns, and build the relation between the primary and foreign keys in the tables. This topic introduces the workflow for Designer to get data from JSON data sources.
This topic contains the following sections:
JSON metadata contains a root element whose element type can be object class or object array. An object class or object array element contains some elements whose element type can be object class, object array, attribute, or simple data array with the data type of String, Number, or Boolean. JSON objects in an array should have the same structure, the members (name/value pairs) in an object cannot be of the same name, and for a nested array, only the first layer is kept.
Designer uses these rules to extract metadata from JSON data:
- Designer extracts elements from the root value of the JSON data hierarchically.
- When Designer creates the root element, the element name is null, and the root element type is object class or object array if the root value of the JSON data is an object class or an object array, else the root element type is an empty object class.
- If the value of an object member is a simple value, Designer creates an attribute element under current element; if it is a simple value array, Designer creates a simple data array element; if it is an object array, Designer creates an object array element; if it is an object class, Designer creates an object class element. Designer sets the element type according to the conversion rules in the Data type conversion table below. The element name is the object member name.
- Designer merges all elements of the same name in object members of an object array into an element.
Before the data types defined in the JSON file can function with Designer, Designer needs to convert them into corresponding SQL data types while extracting metadata from the JSON data, based on the rules in the following table.
|JSON Data Type||SQL Data Type|
|String (following the format Combined date and time representations in ISO 8601)||TIMESTAMP|
|String (following JDBC Timestamp escape format)||TIMESTAMP|
|String (following the format Calendar dates in ISO 8601)||DATE|
|String (following the format Times with time zone designators in ISO 8601)||TIME|
|Number (excluding fraction and exponent)||INTEGER|
|Number (including fraction and exponent)||NUMERIC|
- If the data type of all values for members of the same name in an object array is Number, including not only integer, but also fraction or exponent, Designer converts the data type of all values to NUMERIC.
- If the values for members of the same name in an object array are of different data types and at least one of them is String, Designer converts the data type of all values to VARCHAR.
- You cannot mix the values for the members of the same name in a JSON schema with simple data array or single value, such as String, Number, Boolean, or Null; otherwise, the extracted schema is incorrect.
When Designer transforms JSON schemas to relational schemas, it transforms elements in the JSON schemas to either tables or columns in tables based on the ideographic transformation rules, and names them according to the naming rules.
Designer uses these rules when transforming JSON schemas to relational schemas:
- If an object class or object array element has at least one attribute element or simple data array element, or its embedded element can be mapped to tables, Designer maps the object class or object array element to a table, and its attribute or simple data array element to columns in the table.
- When mapping an attribute element to a column, Designer sets the value of its Mapped SQL Type as the value of the SQL Type of the column.
- For an embedded object class or object array element, Designer creates a built-in column called foreign key for the mapped table. If there is no built-in column called primary key in its parent element table, Designer creates the column. The SQL type of the columns primary key and foreign key is SQL type 4 (64 bit Integer).
Designer names the relational tables and columns in tables based on the following rules:
- For the root element, the table name is ROOT. If the name is not unique, Designer adds the character "_ " before the name one by one until it is unique.
- For elements other than the root element, the table name is the element name. If the table name is not unique, Designer adds the names of the ancestor elements before the table name one by one and separate them by "_" until it is unique.