Correct issue #176: Ensure database setup before building select #197
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
|
Thanks for the pull request - this looks nice. |
treffynnon
added a commit
that referenced
this pull request
May 28, 2014
Correct issue #176: Ensure database setup before building select
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
fixes #176
It appears that when not explicitly setting the database connection via
ORM::set_db(), callingORM::for_table()would not set up the database explicitly. This caused a situation where the database was getting set after the select statement was built, causing the limit clause to be built incorrectly. I also modified the existing test to accurately reflect the situation where this bug appeared.