Conversation
Pin the workspace to drizzle-orm and drizzle-kit 1.0.0-beta.19 so the repo is aligned on the beta-only migration target. Move drizzle-zero onto a prerelease version to land the breaking change on a dedicated release line.
Centralize beta Drizzle column normalization so the rest of the migration can resolve arrays, enums, and extended data types consistently. This keeps runtime type resolution stable while moving away from legacy column internals.
Move the type-level column mapping onto beta Column metadata so custom types, enums, arrays, and logical Zero defaults are resolved from built columns instead of legacy internals. This keeps the migration aligned across tables and schema type helpers before the runtime table builder switches over.
Route Zero table generation through the beta column helpers so arrays, enums, and SQL fallbacks resolve consistently at runtime. This preserves the existing table-shaping rules while moving the runtime path off legacy Drizzle type assumptions.
Build relationships from beta defineRelations and defineRelationsPart exports so direct and through hops share one normalization path. Drop legacy relations and removed manyToMany config support to align the schema generator with the beta-only release target.
Move the relation fixture suite onto defineRelations and through so the regression coverage matches the beta-only schema format. Remove legacy manyToMany and reverse-inference fixtures to keep the remaining tests focused on the supported relation model.
Move the integration schema and generator paths onto beta defineRelations and through so generated relationships come from the supported Drizzle 1.0 model. Fix the related custom-type regressions for nullable string enums and array-typed jsonb fields so the generated Zero schema stays stable.
Update the README to document the beta-only relation APIs, through-based many-to-many setup, and the removed legacy configuration paths. Add explicit upgrade notes so users can move from legacy relations onto the supported Drizzle beta workflow.
Member
Author
|
A new version, |
|
The PR I was going to submit does some gymnastics to simultaneously support either V1 or V2 tables, if you would like me to link you to the code. |
Member
Author
|
It became too complex to support both. I wanted that and started down that road, but the code was too complex. |
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
2 participants
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 is tracking the upcoming
drizzle-ormv2 relations andbetareleases.Install this version with:
Feel free to leave comments on this PR.