We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is a random idea about general system variable concept.
It may be overgeneralize for current status, but I think it is worth to remember when feature enhancement become hard.
This issue is forked from this comment: #183 (comment)
Although spanner-cli has evolved alongside Cloud Spanner as a product, it can be difficult to extend its functionality consistently.
These could be barriers to future feature expansion.
I assume that introducing general system variable may solve some problem.
SET
SHOW VARIABLE
-v assignment
--set=assignment
--variable=assignment
\v{VARIABLE_NAME}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It is a random idea about general system variable concept.
It may be overgeneralize for current status, but I think it is worth to remember when feature enhancement become hard.
This issue is forked from this comment: #183 (comment)
Motivation
Although spanner-cli has evolved alongside Cloud Spanner as a product, it can be difficult to extend its functionality consistently.
These could be barriers to future feature expansion.
I assume that introducing general system variable may solve some problem.
SET
, andSHOW VARIABLE
.-v assignment
--set=assignment
--variable=assignment
SET
statement can be used in spanner-cli session.\v{VARIABLE_NAME}
.SHOW VARIABLE
statement can display system variable value as on-demand.The text was updated successfully, but these errors were encountered: