Changes between Version 1 and Version 2 of Ticket #8576, comment 10
- Timestamp:
- May 2, 2024, 9:28:13 PM (6 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #8576, comment 10
v1 v2 19 19 We have the following options: 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 2. Refactor auto fields so that they are either primary keys OR part of a composite primary key. This addresses my use case, but not the others.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 22 3. Don't use auto fields in composite primary keys. We need an alternative in this case (e.g. https://code.djangoproject.com/ticket/27452).