-
Notifications
You must be signed in to change notification settings - Fork 145
feat(sqla-core): Add support for rendering Database Specific queries #291
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
feat(sqla-core): Add support for rendering Database Specific queries #291
Conversation
Codecov Report
@@ Coverage Diff @@
## master #291 +/- ##
==========================================
+ Coverage 32.04% 32.16% +0.12%
==========================================
Files 84 84
Lines 3305 3308 +3
==========================================
+ Hits 1059 1064 +5
+ Misses 2246 2244 -2
Continue to review full report at Codecov.
|
I'll restructure this PR after the sqla 1.4 PR is merged, as our test restructures will conflict pretty heavily |
@cybojenix Thanks. I'll take a look once it is ready. :) |
Over to you, @srprash |
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.
Just a minor comment. Otherwise LGTM! Thanks!
And could you also update the branch? Thanks! |
by default it runs 9.4. We need to use a feature added in 9.5
This makes the sqla-core plugin aware of how to compile a database specific query. It seems in some cases, we see strings come through (mostly pragma calls when doing 'create_all'), so do a check to see if the object looks like a SQL Expression object. Fixes: #290
this reduces duplication of the Engine fixture.
Both addressed |
Awesome! thanks |
…ws#291) * chore(sqla_core): setup an area to run postgres tests * fix: run a supported version of postgres in travis by default it runs 9.4. We need to use a feature added in 9.5 * feat(sqla-core): Add support for rendering Database Specific queries This makes the sqla-core plugin aware of how to compile a database specific query. It seems in some cases, we see strings come through (mostly pragma calls when doing 'create_all'), so do a check to see if the object looks like a SQL Expression object. Fixes: aws#290 * fix: remove a spurious 'self' in the fixtures * chore: make the DB URL injectable this reduces duplication of the Engine fixture.
Issue: #290
Description of changes:
This makes the sqla-core plugin aware of how to compile a database specific query.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
fixes: #290