SQLite: allow opting out of RETURNING for virtual tables #29679
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Leaving a hook for checking for a table-based opt out of RETURNING Fixes dotnet#29512
roji
changed the title
|
Closing this in favor of #29917 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Leaving a hook for checking for a table-based opt out of RETURNING.
@bricelam this is the update pipeline work necessary to fix #29512, i.e. switch between the new RETURNING syntax and the older multi-command SELECT syntax. We now have to decide if we want to add metadata (and migrations) support for virtual columns, or just add a generic opt out of RETURNING. Feel free to push code into this PR (e.g. virtual table metadata/migrations support).
Fixes #29512