Add custom Introspector class to allow transactions #24
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
|
Would this be a breaking change? (Because of the kysely-d1 version bump?) |
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.
exampleproject.Description
This dialect used the built-in Kysely
SqliteIntrospectorclass as its introspector, which under the hood makes queries to thesqlite_mastertable, which in D1 is a no go - I've extendedSqliteIntrospectorinto aD1Introspectorto support using thetable_listandtable_infoPRAGMAs to query table metadata instead.Also, I've bumped up the version of
kyselyto the latest while I'm here as there were type discrepancies between0.23.3and0.26.3.