> 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
