DuckDB support #857
Merged
DuckDB support #857
Conversation
This file contains hidden or 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
(for start using PostgreSQL keywords and function names lists)
Instead of the array-slice operator (which for now doesn't quite work.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
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.
Created a brand new DuckDB configuration to replace the old #738 pull request.
This should now support the most important bits of DuckDB. There are some caveats though:
LIMIT 10%(conflicts with modulo operator).$foo(conflicts with $$-quoted strings).:in struct literals and prefix aliases).There's definitely quite a bit more than the above three little things. But I think at least for start we have some DuckDB support that should work for most users.