Changes between Initial Version and Version 1 of Ticket #36401
- Timestamp:
- May 19, 2025, 4:49:14 PM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36401
- Property Summary Adding CompositePrimaryKey to exiting table leads to drop existing PK with not composit PK creation → Adding CompositePrimaryKey to existing table leads to drop existing PK with not composite PK creation
-
Ticket #36401 – Description
initial v1 83 83 Expected no matter is model created in one or two steps, final db table will have same PK constraints, eg. CompositePrimaryKey will be created if we add it to existing table. 84 84 85 Issue presented at least in postgres and sqlite 85 Issue presented at least in postgres and sqlite.