Skip to content
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

feat(spanner/spansql): Add tests and parser support for THEN RETURN #6515

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

c2nes
Copy link

@c2nes c2nes commented Aug 15, 2022

This change adds THEN RETURN support for DML statements. The existing "Query" methods already support executing such statements, so this change is limited to updating documentation, adding integration tests, and updating the spansql package. Support has not been added to the spannertest in-memory implementation of Spanner, but the feature absence has been noted in the corresponding README.

@c2nes c2nes requested review from a team as code owners August 15, 2022 14:07
@product-auto-label product-auto-label bot added the size: l Pull request size is large. label Aug 15, 2022
@ansh0l ansh0l requested a review from rahul2393 August 15, 2022 14:08
@c2nes
Copy link
Author

c2nes commented Aug 15, 2022

Note: Integration tests are not expected to pass until THEN RETURN support is launched.

@quartzmo quartzmo added the api: spanner Issues related to the Spanner API. label Aug 16, 2022
@codyoss codyoss changed the title feat: Add tests and parser support for THEN RETURN feat(spanner/spansql): Add tests and parser support for THEN RETURN Aug 22, 2022
@@ -24,6 +24,7 @@ by ascending esotericism:
- SELECT HAVING
- more literal types
- DEFAULT
- THEN RETURN
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are supporting it through this PR, right? I guess we want to say PG.Returning is not supported.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I did not intend to add this support myself. We will be adding support to the standard Spanner Emulator however.

@c2nes c2nes force-pushed the dml-then-return branch 2 times, most recently from c4e306b to 71a8c62 Compare August 30, 2022 20:45
This change adds THEN RETURN support for DML statements. The existing
"Query" methods already support executing such statements, so this
change is limited to updating documentation, adding integration tests,
and updating the spansql package. Support has not been added to the
spannertest in-memory implementation of Spanner, but the feature absence
has been noted in the corresponding README.
@rahul2393 rahul2393 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 2, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 2, 2022
@rajatbhatta rajatbhatta added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Sep 2, 2022
@product-auto-label product-auto-label bot added the stale: old Pull request is old and needs attention. label Sep 15, 2022
@product-auto-label product-auto-label bot added stale: extraold Pull request is critically old and needs prioritization. and removed stale: old Pull request is old and needs attention. labels Oct 15, 2022
@rahul2393 rahul2393 added kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed do not merge Indicates a pull request not ready for merge, due to either quality or timing. labels Nov 3, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Nov 3, 2022
@codyoss
Copy link
Member

codyoss commented Jul 24, 2024

@rahul2393 are there still plans to accecpt this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the Spanner API. size: l Pull request size is large. stale: extraold Pull request is critically old and needs prioritization.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants