Yes, I have read that thread. But since BigIntegerField is now available within Django, I would like to handle it from within Django itself.
Thus I want to knowif changing the contrib.auth code to explicitly include a BigIntegerField primary key will have any side-effects (for example in contrib.admin or elsewhere). On Jan 9, 4:06 am, Rolando Espinoza La Fuente <dark...@gmail.com> wrote: > An option is to just use ALTER TABLE.. command to change the column type. > > Regards, > > ref:http://www.mail-archive.com/django-develop...@googlegroups.com/msg211... > > On Fri, Jan 8, 2010 at 5:51 AM, G B Smith <greenblanket.sm...@gmail.com> > wrote: > > > > > Greetings, > > > Let's say I know that the number of users of my app is going to be > > very really really high. And let's also say I want to use the > > contrib.auth as it is so convenient. > > > Is it okay if I simply change the code of django.contrib.auth.user to > > explicitly include an BigIntegerField called id and manually set it to > > be an auto-incrementing primary key? > > > Will this have any side effects that I am not aware of? > > > GBS. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/django-users?hl=en. > > -- > Rolando Espinoza La fuentewww.rolandoespinoza.info
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
