Reference documentation and code samples for the Cloud Spanner V1 Client class TypeAnnotationCode.
TypeAnnotationCode
is used as a part of 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.
Protobuf type google.spanner.v1.TypeAnnotationCode
Namespace
Google \ Cloud \ Spanner \ V1Methods
static::name
Parameter | |
---|---|
Name | Description |
value |
mixed
|
static::value
Parameter | |
---|---|
Name | Description |
name |
mixed
|
Constants
TYPE_ANNOTATION_CODE_UNSPECIFIED
Value: 0
Not specified.
Generated from protobuf enum TYPE_ANNOTATION_CODE_UNSPECIFIED = 0;
PG_NUMERIC
Value: 2
PostgreSQL compatible NUMERIC type. This annotation needs to be applied to Type instances having 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 when a client interacts with PostgreSQL-enabled Spanner databases.
Generated from protobuf enum PG_NUMERIC = 2;
PG_JSONB
Value: 3
PostgreSQL compatible JSONB type. This annotation needs to be applied to Type instances having 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 when a client interacts with PostgreSQL-enabled Spanner databases.
Generated from protobuf enum PG_JSONB = 3;
PG_OID
Value: 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.
Generated from protobuf enum PG_OID = 4;