feat(sqlite): add native STRICT table support#5907
Draft
agustif wants to merge 1 commit into
Draft
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
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.
Summary
Adds first-class SQLite
STRICTtable support to the currentbetaarchitecture.Drizzle Kit emits
STRICT, preserves the metadata through snapshots, diffs, introspection, pull code generation, and recreate-table migrations, and rejects unsupported SQLite storage classes before SQL generation.Compatibility
drizzle-kit upupgrades v5/v6/v7 histories and defaults existing tables toisStrict: false.text(N)metadata is emitted as SQLiteTEXTin strict tables so the generated SQL uses an allowed strict storage class; Effect Schema still derives the declared text limit.Validation
drizzle-ormtype tests passed.Existing work
This is the beta-branch implementation of the same feature area as #5389 and the earlier #202 request. #5389 targets the older
mainKit architecture; this PR carries the feature through the current beta DDL/snapshot pipeline, including v8 upgrades, strict toggles, pull generation, and invalid-type validation.