Skip to content

docs: Update migration guide for primary key column rules #209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 29, 2025
+1 −1
Merged

docs: Update migration guide for primary key column rules #209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guides/migration/v1-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ nullability now becomes opt-in.
### Primary key columns may not be nullable

While dataframely v1 merely emitted a warning, dataframely v2 now raises an exception if a primary key is designated
as non-nullable. This aligns dataframely, for example, with SQL where primary key columns may not be nullable.
as nullable. This aligns dataframely, for example, with SQL where primary key columns may not be nullable.

### Schema rules are now defined as classmethods

Expand Down
Loading