-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Protocol Buffers #174
Comments
Then, there might be two possible ways:
I think the first option is not intuitive. For second option, I don't think users will use that option if the same functionality is available in gcloud. Overall, my impression is that we can ask users to use gcloud if they want to run |
I agree What about Current behaviour of
|
Is this output a bit long? |
Yes, I agree that we should decode PROTO and ENUM typed values properly, but showing the proto field name looks a bit too much. If users want to check an actual value, they might use |
I agree FQN type name is too long and the same printing as Spanner Studio is a good choice. |
This is a very edge case, but it could be confusing if a STRING value contains "AS" in the value.
So I'm not sure if it's a good idea to annotate the value with a proto type. |
I often read databases whose schemas I didn't know, so I was worried about outputting raw values that couldn't be read without knowledge of the schemas. |
Protocol Buffers support is already GA.
We can discuss initial support of Protocol Buffers in spanner-cli.
CREATE PROTO BUNDLE
gcloud spanner databases ddl update DATABASE_NAME --instance=INSTANCE_NAME --ddl='CREATE PROTO BUNDLE (
examples.shipping.Order);' --proto-descriptors-file=order_descriptors.pb
--execute
.ENUM
s.The text was updated successfully, but these errors were encountered: