I agree with Loïc that this problem is probably best solved when the
virtual/composite stuff is finally sorted out; I don't want us to put in a
quicker fix that's not going to match those, and that's already going to
have to deal with things like composite keys and potentially changing FKs
anyway.
I think we can link https://code.djangoproject.com/ticket/56 to
https://code.djangoproject.com/ticket/14286.
The problem is not so much how to create an UnsignedAutoField or a BigAutoField
which is rather trivial, but how to deal with foreign keys pointing to them and
how to migrate them. As fa
I've picked up this old ticket:
https://code.djangoproject.com/ticket/56
After some initial discussions on #django-dev it seems like wontfixing it
would be an option too, so I wanted to ask about core devs' view on this:
Is implementing opt-in support for unsigned primary keys on MySQL still
int
