Skip to content
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

fix conflicting use of query #247

Merged
merged 4 commits into from
Jul 17, 2018
Merged

Conversation

drujensen
Copy link
Member

@drujensen drujensen commented Jun 27, 2018

renamed the macro to select_statement so it won't conflict with the pass-through query method. fixed #246

@drujensen drujensen requested review from damianham, robacarp, faustinoaq and a team June 27, 2018 02:35
Copy link
Contributor

@damianham damianham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be worthwhile adding something to the test suite to ensure Model.query("select fields from table") isn't broken by any future update

@drujensen
Copy link
Member Author

@damianham 👍 right. I will add one for each pass-through.

Copy link
Member

@robacarp robacarp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 when there's a test too!

@drujensen
Copy link
Member Author

@damianham @robacarp added tests for the passthroughs.

@drujensen drujensen merged commit d6a758b into master Jul 17, 2018
@drujensen drujensen deleted the dj/rename-query-to-select-statement branch July 17, 2018 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unable to run an arbitrary query
3 participants