Eric, could you explain how this UUID implementation was achieved? Django doesn't have a built-in UUID, so I can only guess that you used a varchar field within Django. ?
On Jan 10, 2:29 am, Eric Chamberlain <e...@rf.com> wrote: > On Jan 9, 2010, at 8:59 AM, G B Smith wrote: > > > Thanks, that is a good resource. So this is what I am going to do : - > > -- modify the contrib.auth.models.user to explicitly include id = > > models.BigIntegerField(primary_key=True) > > -- modify the contrib.auth.models.user.id field in the database using > > creecode's method above or via the mysql shell or phpmyadmin or other > > tools (still deciding) > > > I am pretty sure this is going to have zero side-effects. If someone > > knows otherwise, would be helpful to have that information. > > If your going to go to all that trouble, you may as well use a UUID field > instead. We went with UUID, because we didn't want membership counts to leak > via an autoincrementing integer. > > -- > Eric Chamberlain, Founder > RF.com -http://RF.com/
-- 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.
