v8.15.1
What's Changed
-
fix(sqlite): emit composite primary keys as table-level constraint by @claude in #262
When a
Weasel.Sqlite.Tables.Tablehad two or more columns each calling.AsPrimaryKey(), the generated DDL emitted an inlinePRIMARY KEYon every PK column. SQLite rejects that with'table … has more than one primary key'and the migration aborts before the table is ever created. The fix detects the composite-PK case and emits a single table-levelCONSTRAINT pk_<table> PRIMARY KEY (col1, col2)clause instead. Single-column PKs are unchanged. Surfaces downstream as JasperFx/wolverine#2680 — bumping the WolverineFx.Sqlite Weasel dependency to this release silently fixes the bug.
Full Changelog: v8.15.0...v8.15.1