I assume you could checksum some form of the user's object or
"cleaned" form values and store it as unique attribute of the users.
You would prolly have to override the clean method and add in
valudation of the uniqueness and generate using an alternate method if
the first does not validate unique, the main issue I see is needing to
get that value for the UUID unique every time. Could be as simple as
salting the username with timestamp and checksumming the text. pad or
trim to get the necessary length, but this doesnt seem necessary.
Since your not using a base 10 character system anymore you can really
increase the max number of users by alot without using a ton of space
storing digits.
One impact may be lookup time and index storage/maintenance as your
uuid field would probably benefit from an index to reduce search time.
With an "astronomically high number of users" I imagine your
production equipment would need to be pretty serious already.
On Jan 9, 2010, at 9:56 PM, G B Smith wrote:
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
.
--
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.
