On Sat, Aug 1, 2015 at 4:53 AM, James Schneider <[email protected]> wrote: > If you are talking about potentially having enough rows to extend past the > AutoPK limits, you should consider instead using a UUID field as the PK:
note that this is only good advice if your DB handles it natively. if not, Django will use a charField to store it and constantly encode-decode it. If you're using PosgreSQL, then yes, UUID is great; on MySQL, then it's far more efficient to use a BigInteger. 2^64 records still is far more than what you can store in the biggest storage you can get. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoRzx3m%2B4rYuppJw_hWtt552tVG769B67RuOj8EdJCrQsg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
