Ambiguity between a JSON Dot Notation Reference and References to Other Database Objects - 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

The syntax for JSON dot notation, a Vantage ARRAY type element reference, and a fully or partially qualified column reference is similar. This creates potential ambiguity in the following cases:

  1. Ambiguity between a Vantage ARRAY type element reference and a JSON type array reference
  2. Ambiguity between a fully or partially qualified column reference and a JSON type dot notation reference
When there is ambiguity, the default interpretation of the syntax is as follows:
  • For case 1: The syntax is interpreted as a Vantage ARRAY type element reference.
  • For case 2: The syntax is interpreted as a fully or partially qualified column reference.

Handling of these potential ambiguities is described in more detail in the following sections.

To make sure that a JSON dot notation reference is not ambiguous, fully qualify a JSON column being referenced. Alternatively, you can use the JSONExtract, JSONExtractValue, or JSONExtractLargeValue methods to retrieve entities of a JSON instance.