fix: Error on select after delete or update #17
Merged
Conversation
This file contains hidden or 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
Track updated rows and return with response Fixes supabase-community#16
Track removed rows and return with response Fixes supabase-community#16
Always return inserted record(s) as list with response Fixes supabase-community#16
dshukertjr
approved these changes
Mar 5, 2025
dshukertjr
changed the title
It was my privilege to help. |
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.
What kind of change does this PR introduce?
This PR ensures that fetching records after insert, update and delete using
selectwork as expected.What is the current behavior?
See Issue #16
What is the new behavior?
The insert, update and delete operations all function as expected when trailed by select .