fix: parse support of delete() functions - #774
Merged
Merged
Conversation
Ensure array- and hstore-argument variants remain valid function calls during statement splitting.
psteinroe
approved these changes
Jul 24, 2026
Contributor
Author
|
@psteinroe thanks for merging this one so quickly! When is the next npm release planned? Let me know if there is anything I can help with! |
Collaborator
@lneves12 sorry, I created the draft release on friday but forgot to go through with it. it will be there any minute! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Extensions like hstore or custom functions named delete break the parser as the parser thinks the token is a delete from statement
What is the current behavior?
Extensions like hstore or custom functions named delete break the parser as the parser thinks the token is a delete from
What is the new behavior?
Checks if the next character is a ( to distinguish both tokens