Changes between Version 5 and Version 6 of Ticket #8576, comment 10
- Timestamp:
- May 6, 2024, 11:19:15 AM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #8576, comment 10
v5 v6 1 https://code.djangoproject.com/ticket/3731 #373 2 2 I'm looking to implement composite primary keys like this: 3 3 … … 20 20 1. Remove the limitation for databases that support non-primary auto fields altogether. We could allow non-primary key auto fields for PostgreSQL, for example. 21 21 2. On top of (1), refactor auto fields so that they are either primary keys OR part of a composite primary key. This adds a further limitation to address my use case, but not the others. 22 3. Don't use auto fields in composite primary keys. We need an alternative in this case (e.g. SERIAL in contrib.postgres https://code.djangoproject.com/ticket/27452).22 3. Don't use auto fields in composite primary keys. We need an alternative in this case (e.g. SERIAL in contrib.postgres #27452). 23 23 24 24 IMO either (1) or (3) (or both) are a good solution.