On Oct 7, 10:16 pm, indymike <[email protected]> wrote: > Here's my issue - I'm going to run out of integers for my primary key > in one of my tables. I'm using MySQL, which has been absolutely > fantastic, and will for at least a few more decades if I can make a > change from INT to BIGINT. > > What's the right way to switch from INT to BIGINT so the PK works > correctly? > > / First thought was a big, fat south migration, but I I wonder if > there's anything in Django's code that this will break?
Found this: http://stackoverflow.com/questions/283724/big-integer-field-in-django-models which implies it should "just work" from version 1.2 onwards. Be aware that Django's sync method wil create the PK field with a default of int(11), not bigint, so you'll need to change that in the database itself. -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
