-
Notifications
You must be signed in to change notification settings - Fork 609
Support INSERT INTO ... DEFAULT VALUES ...
#1036
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
Merged
alamb
merged 4 commits into
apache:main
from
cipherstash:postgres-insert-default-values
Nov 21, 2023
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
095d108
Support `INSERT INTO ... DEFAULT VALUES ...`
CDThomas 4f334bd
Fix bug where columns could be listed after `DEFAULT VALUES`
CDThomas cc9cc5f
Merge in main and resolve conflicts in MySQL tests
CDThomas 63f8a6c
Remove extra whitespace in `DEFAULT VALUES ON CONFLICT` test
CDThomas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should never print
INSERT INTO my_table(my_column);
, which is syntactically invalid.INSERT INTO my_table(my_column) DEFAULT VALUES;
should successfully round-trip through sqlparser, since it's a logical error, but not a syntax error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @lovasoa.
I thought about this a bit and double checked the SQL grammar and implementation in Postgres and both seem to make
INSERT INTO my_table(my_column) DEFAULT VALUES;
invalid at the syntax level. I think it'd make sense for sqlparser to make this scenario a syntax error as well, but I could be missing something.I also tested a statement out with Postgres in a DB fiddle and confirmed that it raises a syntax error:
What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right about postgres, but it's not a syntax error in sqlite.
And
insert into t(x);
is a syntax error everywhere anyway, so I think we should never emit that.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah interesting, I was not aware of the behaviour in SQLite.
I added some coverage for syntax errors with
DEFAULT VALUES
here. Do you think that behaviour looks reasonable?