> Django is optimized for the common case. Sure, it may well be that
> it's easy to accommodate uncommon cases as well, and when it's
> reasonable, we should definitely do so, but the reason it hasn't been
> up to this point is simply that not enough people need it.
I agree fully. I've only need
Now for some leg work.
The simple part is to remove the primary key assert in
AutoField.__init__.
The hard part is that django creates tables with multiple sql
statements. One for the table create and then one for each index.
MySQL requires that auto_increment fields must be indexed. Since
dja
> 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
In ticket #8576 a request was made to remove the restriction that
AutoFields must be primary keys so that multiple AutoFields could be
used in a model. In MySQL multiple auto-increment fields does not
make sense and probably does not make sense in any other database.
However, I do think the case
