Static Fields
|
---|
Name | Description |
ARRAY | Encoded as list , where the list elements are represented
according to
array_element_type.
ARRAY = 8;
|
ARRAY_VALUE | Encoded as list , where the list elements are represented
according to
array_element_type.
ARRAY = 8;
|
BOOL | Encoded as JSON true or false .
BOOL = 1;
|
BOOL_VALUE | Encoded as JSON true or false .
BOOL = 1;
|
BYTES | Encoded as a base64-encoded string , as described in RFC 4648,
section 4.
BYTES = 7;
|
BYTES_VALUE | Encoded as a base64-encoded string , as described in RFC 4648,
section 4.
BYTES = 7;
|
DATE | Encoded as string in RFC 3339 date format.
DATE = 5;
|
DATE_VALUE | Encoded as string in RFC 3339 date format.
DATE = 5;
|
FLOAT64 | Encoded as number , or the strings "NaN" , "Infinity" , or
"-Infinity" .
FLOAT64 = 3;
|
FLOAT64_VALUE | Encoded as number , or the strings "NaN" , "Infinity" , or
"-Infinity" .
FLOAT64 = 3;
|
INT64 | Encoded as string , in decimal format.
INT64 = 2;
|
INT64_VALUE | Encoded as string , in decimal format.
INT64 = 2;
|
JSON | Encoded as a JSON-formatted string as described in RFC 7159. The
following rules are applied when parsing JSON input:
- Whitespace characters are not preserved.
- If a JSON object has duplicate keys, only the first key is preserved.
- Members of a JSON object are not guaranteed to have their order
preserved.
- JSON array elements will have their order preserved.
JSON = 11;
|
JSON_VALUE | Encoded as a JSON-formatted string as described in RFC 7159. The
following rules are applied when parsing JSON input:
- Whitespace characters are not preserved.
- If a JSON object has duplicate keys, only the first key is preserved.
- Members of a JSON object are not guaranteed to have their order
preserved.
- JSON array elements will have their order preserved.
JSON = 11;
|
NUMERIC | Encoded as string , in decimal format or scientific notation format.
<br>Decimal format:
<br>[+-]Digits[.[Digits]] or
<br>+-.Digits
Scientific notation:
<br>[+-]Digits[.[Digits]][ExponentIndicator[+-]Digits] or
<br>+-.Digits[ExponentIndicator[+-]Digits]
<br>(ExponentIndicator is "e" or "E" )
NUMERIC = 10;
|
NUMERIC_VALUE | Encoded as string , in decimal format or scientific notation format.
<br>Decimal format:
<br>[+-]Digits[.[Digits]] or
<br>+-.Digits
Scientific notation:
<br>[+-]Digits[.[Digits]][ExponentIndicator[+-]Digits] or
<br>+-.Digits[ExponentIndicator[+-]Digits]
<br>(ExponentIndicator is "e" or "E" )
NUMERIC = 10;
|
STRING | Encoded as string .
STRING = 6;
|
STRING_VALUE | Encoded as string .
STRING = 6;
|
STRUCT | Encoded as list , where list element i is represented according
to [struct_type.fields[i]][google.spanner.v1.StructType.fields].
STRUCT = 9;
|
STRUCT_VALUE | Encoded as list , where list element i is represented according
to [struct_type.fields[i]][google.spanner.v1.StructType.fields].
STRUCT = 9;
|
TIMESTAMP | Encoded as string in RFC 3339 timestamp format. The time zone
must be present, and must be "Z" .
If the schema has the column option
allow_commit_timestamp=true , the placeholder string
"spanner.commit_timestamp()" can be used to instruct the system
to insert the commit timestamp associated with the transaction
commit.
TIMESTAMP = 4;
|
TIMESTAMP_VALUE | Encoded as string in RFC 3339 timestamp format. The time zone
must be present, and must be "Z" .
If the schema has the column option
allow_commit_timestamp=true , the placeholder string
"spanner.commit_timestamp()" can be used to instruct the system
to insert the commit timestamp associated with the transaction
commit.
TIMESTAMP = 4;
|
TYPE_CODE_UNSPECIFIED | Not specified.
TYPE_CODE_UNSPECIFIED = 0;
|
TYPE_CODE_UNSPECIFIED_VALUE | Not specified.
TYPE_CODE_UNSPECIFIED = 0;
|
UNRECOGNIZED | |