On Mon, 2008-07-07 at 10:09 -0700, digitalxero wrote: [...] > The issue may actually be with the get_or_create() method of blocking > collisions since if it generates a duplicate id it just grabs that > data from the table and runs with it (I think), but whatever the > actual cause of the issue the latest patch prevents it on my setup.
Yes. It's important to view things like this thread in the context of the earlier thread about session fixes. There are a number of inter-related things here and a fix that solves the general problem instead of playing whack-a-mole is in order. Part of that, and implicit in this whole thing, is ensuring that the new session id is saved (and *created*) immediately to avoid collisions. The database is the only way to ensure uniqueness here and there is a bug at that level. Increasing some value from 32 bits to 64 bits is only changing some probabilities; it's not actually solving the problem, just moving the goalposts to make it harder to score an own goal. The rest of the conversation should proceed on the assumption that the bug about creating unique database entries will be fixed first. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
