- 3.46.0 (latest)
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.1
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.1
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.27.1
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.2
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.1
- 3.14.1
- 3.13.0
- 3.12.1
- 3.11.1
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.1.1
- 2.0.0
- 1.19.3
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.1
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
TypeAnnotationCode(value)TypeAnnotationCode is used as a part of
Type][google.spanner.v1.Type] to disambiguate SQL types that should
be used for a given Cloud Spanner value. Disambiguation is needed
because the same Cloud Spanner type can be mapped to different SQL
types depending on SQL dialect. TypeAnnotationCode doesn't affect
the way value is serialized.
Enum values:
TYPE_ANNOTATION_CODE_UNSPECIFIED (0):
Not specified.
PG_NUMERIC (2):
PostgreSQL compatible NUMERIC type. This annotation needs to
be applied to `Type][google.spanner.v1.Type]` instances
having `NUMERIC][google.spanner.v1.TypeCode.NUMERIC]` type
code to specify that values of this type should be treated
as PostgreSQL NUMERIC values. Currently this annotation is
always needed for
`NUMERIC][google.spanner.v1.TypeCode.NUMERIC]` when a client
interacts with PostgreSQL-enabled Spanner databases.
PG_JSONB (3):
PostgreSQL compatible JSONB type. This annotation needs to
be applied to `Type][google.spanner.v1.Type]` instances
having `JSON][google.spanner.v1.TypeCode.JSON]` type code to
specify that values of this type should be treated as
PostgreSQL JSONB values. Currently this annotation is always
needed for `JSON][google.spanner.v1.TypeCode.JSON]` when a
client interacts with PostgreSQL-enabled Spanner databases.
PG_OID (4):
PostgreSQL compatible OID type. This
annotation can be used by a client interacting
with PostgreSQL-enabled Spanner database to
specify that a value should be treated using the
semantics of the OID type.