add support for libSQL dialect #3977
Open
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
Signed-off-by: Golang Lemonade <[email protected]>
golanglemonade
force-pushed
the
libsql-support
branch
from
b3eec24
to
a3375ff
Compare
|
I would love this feature ❤️ |
|
👀 |
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.
We are using
atlasfor migrations, which has support forlibsql, a fork of SQLite, however, today you cannot use versioned migrations because it uses ent, which doesn't support thelibsqldialect. This PR adds the libSQL dialect, but uses all the same code-paths as SQLite.Since libSQL is a fork of SQLite, I didn't find it necessary to create an entirely different
sql/schematype, but happy to hear other opinions.Relates to ariga/atlas#2338