JSON Data Type | Restrictions | VantageCloud Lake - Restrictions for the JSON Type - Teradata Vantage

Teradata® VantageCloud Lake
Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
  • You cannot specify the JSON type in the following situations:
    • As the base type of a distinct UDT
    • As the element type of an ARRAY type
  • You cannot create methods for the JSON type. Therefore, you cannot specify a JSON type name in the FOR clause of a CREATE/REPLACE METHOD statement.
  • You cannot specify a JSON type column as part of an index, although a non-LOB JSON type may be part of a join index (depending on the situation).
  • You cannot use JSON type columns in clauses that depend on ordering or comparison, such as ORDER BY, GROUP BY, or HAVING.
  • You cannot update the entities of a JSON instance. Therefore, you cannot use JSON dot notation in the target portion of a SET clause.
  • Although the external representation of JSON values is of the character string type, string operations are not allowed directly on the JSON values. JSON can be serialized or cast to generate a string representation before you apply the string operation.
  • Extracted JSON values can be used in arithmetic expressions. You can cast the extracted JSON value to the appropriate SQL type to perform the computation.
  • Extracted JSON values can be used in relational comparison operations (such as >, <, or =). You can cast the extracted JSON value to the appropriate SQL type to perform the comparison.
  • JSON type columns cannot do the following.
    • Occur in queue tables
    • Participate in joins; however, portions of the JSON column can be joined and JSON columns can be in the SELECT list