Repository navigation
Keep generate names distinct and render SQLite constraints in statements - #495
Merged
Merged
Conversation
…statements. Version snapshots compare authored YAML, colliding User types export without overwriting, leftover generate files stay unless --delete, and SQLite unique/FK changes become indexes or a table rebuild instead of ALTER CONSTRAINT. Co-authored-by: Cursor <cursoragent@cursor.com>
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
generate --delete(default false) prunes leftover output files; unique and foreign-key changes render in SQLite as indexes or a table rebuild, notALTER CONSTRAINT.Test plan
npm test, CLI generate/Rust compile, C# SQLite renderer and schema-diff)generate all --dialect typescript --no-auto-migrate-upon user-roles after this landsMade with Cursor