SQLAlchemy translator backend and preliminary SQLite client #585
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
…ertain test groups
…column expr working
Closed
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.
Essential refactoring to compartmentalize SQLAlchemy-based translator backends from homegrown ones (like the Impala translator). More code cleaning and reorganization to maximize reuse.
This doesn't have complete support for SQLite SQL keywords and built-in functions yet. I will make some follow up issues to organize the process and address in follow-up pull requests.
Closes #584
This also paves the road to Postgres / Vertica / Redshift / MySQL support in the near future.