Enum TypeAnnotationCode (6.98.1)

public enum TypeAnnotationCode extends Enum<TypeAnnotationCode> implements ProtocolMessageEnum

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 enum google.spanner.v1.TypeAnnotationCode

Implements

ProtocolMessageEnum

Inherited Members

Enum.<T>valueOf(Class<T>,String)

Enum.clone()

Enum.compareTo(E)

Enum.equals(Object)

Enum.finalize()

Enum.getDeclaringClass()

Enum.hashCode()

Enum.name()

Enum.ordinal()

Enum.toString()

Object.getClass()

Object.notify()

Object.notifyAll()

Object.wait()

Object.wait(long)

Object.wait(long,int)

Static Fields
Name	Description
`PG_JSONB`	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. `PG_JSONB = 3;`
`PG_JSONB_VALUE`	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. `PG_JSONB = 3;`
`PG_NUMERIC`	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. `PG_NUMERIC = 2;`
`PG_NUMERIC_VALUE`	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. `PG_NUMERIC = 2;`
`PG_OID`	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. `PG_OID = 4;`
`PG_OID_VALUE`	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. `PG_OID = 4;`
`TYPE_ANNOTATION_CODE_UNSPECIFIED`	Not specified. `TYPE_ANNOTATION_CODE_UNSPECIFIED = 0;`
`TYPE_ANNOTATION_CODE_UNSPECIFIED_VALUE`	Not specified. `TYPE_ANNOTATION_CODE_UNSPECIFIED = 0;`
`UNRECOGNIZED`

Static Methods
Name	Description
`forNumber(int value)`
`getDescriptor()`
`internalGetValueMap()`
`valueOf(Descriptors.EnumValueDescriptor desc)`
`valueOf(int value)`	Deprecated. Use #forNumber(int) instead.
`valueOf(String name)`
`values()`

Methods
Name	Description
`getDescriptorForType()`
`getNumber()`
`getValueDescriptor()`

Enum TypeAnnotationCode (6.98.1) Stay organized with collections Save and categorize content based on your preferences.

Implements

Inherited Members

Static Fields

Static Methods

Methods

Enum TypeAnnotationCode (6.98.1)