Open
Conversation
DSQL only supports 1 DDL statement per transaction, making it hard to support migrations. Remove for now.
Extends DSQL query-builder coverage.
This adds support for generate and push for schema management.
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
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.
This PR adds DSQL support to Drizzle, addresses #5248
DSQL is a postgres-wire compatible database, but with some divergence on features. I think the divergence is enough to require a separate
dsql-coredialect implementation, but most of that implementation has been copied frompg-core.Important divergence includes:
I've added integration tests, although these will require a DSQL cluster endpoint and AWS creds that can access the cluster. I've verified they all pass when run locally