> my records are created in several satellite systems Ah, that is, the legacy database is involved. It makes the example even more vivid - having a legacy primary key while still having the convenience of a non-primary autofield.
I fully agree that we better should NOT add any backend-dependent behaviour. This is not what the ticket suggests, in fact. The ticket is about the unnecessary (in several legal cases) restriction, which is not covered by the documentation yet (or at least was not, when the ticket was raised) at all. So the idea is not to add any backend- specificity - the idea is to remove an unnecessary (at least in some backends) restriction instead, bringing the code back to the documentation, and just refrain from specifying this behaviour. On Mar 1, 6:25 pm, NewSpire <newsp...@gmail.com> wrote: > > MySQL, if I recall correctly, > > flat-out will not support this at all. > > Correct! MySQL definitely does not support multiple auto-increment > fields. However, that is not what I'm talking about. I would just > like the primary key requirement removed from the AutoField. MySQL > definitely does not require that an auto-increment field be a primary > key. I've never used Postgres or Oracle, but I do not see any > indication that they require their sequence fields to be primary keys > either. > > Let me shore up my use case a bit. In my application I cannot have > AutoField primary keys. My primary keys must be UUIDFields. This is > because my records are created in several satellite systems and then > later aggregated back to a central database. If I use AutoFields as > the primary key I would get key violations when the satellite tables > are aggregated into a single central table. This is because I would > have one record in every satellite system with id=1. > > Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
