On Sun, Mar 1, 2009 at 8:25 AM, NewSpire <[email protected]> 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.
The limitation in Oracle is in the backend, not in the database. To support an AutoField, we create a sequence and a trigger, the names of which are derived from the name of the table. To support multiple AutoFields, the names would have to be distinct -- most likely they would be derived from a combination of the names of the table and the column. But for backward compatibility, the backend needs to continue to generate the same sequence name when the model has only one AutoField. That's not impossible, but the refactoring necessary to meet both of those goals is not trivial. Regards, Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
