Skip to content

Commit 64a5bfe

Browse files
Google APIscopybara-github
authored andcommitted
feat(spanner): add proto and enum types
PiperOrigin-RevId: 599046867
1 parent c7985b4 commit 64a5bfe

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

google/spanner/v1/type.proto

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,13 @@ message Type {
4747
// typically is not needed to process the content of a value (it doesn't
4848
// affect serialization) and clients can ignore it on the read path.
4949
TypeAnnotationCode type_annotation = 4;
50+
51+
// If [code][google.spanner.v1.Type.code] ==
52+
// [PROTO][google.spanner.v1.TypeCode.PROTO] or
53+
// [code][google.spanner.v1.Type.code] ==
54+
// [ENUM][google.spanner.v1.TypeCode.ENUM], then `proto_type_fqn` is the fully
55+
// qualified name of the proto type representing the proto/enum definition.
56+
string proto_type_fqn = 5;
5057
}
5158

5259
// `StructType` defines the fields of a [STRUCT][google.spanner.v1.TypeCode.STRUCT] type.
@@ -145,6 +152,13 @@ enum TypeCode {
145152
// preserved.
146153
// - JSON array elements will have their order preserved.
147154
JSON = 11;
155+
156+
// Encoded as a base64-encoded `string`, as described in RFC 4648,
157+
// section 4.
158+
PROTO = 13;
159+
160+
// Encoded as `string`, in decimal format.
161+
ENUM = 14;
148162
}
149163

150164
// `TypeAnnotationCode` is used as a part of [Type][google.spanner.v1.Type] to

0 commit comments

Comments
 (0)