prevent faulty SQL statement when #siblings is called on an unsaved records #52
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
mceachen
added a commit
that referenced
this pull request
Apr 4, 2013
prevent faulty SQL statement when #siblings is called on an unsaved records
|
Wow, this was a perfect pull request. Thanks! |
|
Thanks for the awesome gem! |
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.
Allow #siblings to be called on unsaved models. This becomes relevant when #siblings is used in custom validations (which will run before the model has an ID). This PR fixes the faulty SQL that is constructed by #siblings when the model hasn't yet received an ID.