EF: Fix INSERT INTO with no specified column values, by using DEFAULT VALUES. #310
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
Contributor
Author
|
This fix should be included in 2.2. |
Emill
added a commit
that referenced
this pull request
Aug 5, 2014
EF: Fix INSERT INTO with no specified column values, by using DEFAULT VALUES.
Member
|
Em 05/08/2014 19:55, "Emill" notifications@github.com escreveu:
I'm on it!
|
Member
Done. |
Member
|
@franciscojunior, we have confirmation from the user that the fix is good. I think we can release 2.2 with this even if we don't do another rc... |
Member
Sure! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #233.
Instead of running
which results in parse error, run this instead:
which corresponds to the syntax at http://www.postgresql.org/docs/9.3/static/sql-insert.html.