code property

The TypeCode for this type.

Required. Possible string values are:

• "TYPE_CODE_UNSPECIFIED" : Not specified.
• "BOOL" : Encoded as JSON true or false.
• "INT64" : Encoded as string, in decimal format.
• "FLOAT64" : Encoded as number, or the strings "NaN", "Infinity", or "-Infinity".
• "FLOAT32" : Encoded as number, or the strings "NaN", "Infinity", or "-Infinity".
• "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.
• "DATE" : Encoded as string in RFC 3339 date format.
• "STRING" : Encoded as string.
• "BYTES" : Encoded as a base64-encoded string, as described in RFC 4648, section 4.
• "ARRAY" : Encoded as list, where the list elements are represented according to array_element_type.
• "STRUCT" : Encoded as list, where list element i is represented according to [struct_type.fields[i]][google.spanner.v1.StructType.fields].
• "NUMERIC" : Encoded as string, in decimal format or scientific notation format. Decimal format: [+-]Digits[.[Digits]] or +-.Digits Scientific notation: [+-]Digits[.[Digits]][ExponentIndicator[+-]Digits] or +-.Digits[ExponentIndicator[+-]Digits] (ExponentIndicator is "e" or "E")
• "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.
• "PROTO" : Encoded as a base64-encoded string, as described in RFC 4648, section 4.
• "ENUM" : Encoded as string, in decimal format.