Thus, looks there are two problems -- collisions happen too often on 32-bit machines (fixed by my patch) and db session backend doesn't handle them properly (no fix so far).
As for the latter -- Malcolm, you were about to add a clear distinction between INSERT and UPDATE to .save() in http://groups.google.com/group/django-developers/browse_thread/thread/179ed55b3bf44af0 . That would help to fix def save(self): Session.objects.create( session_key = self.session_key, session_data = self.encode(self._session), expire_date = self.get_expiry_date() ) As far as I can see, create uses .save() and .save() does an UPDATE when the object exists instead of unconditionally failing as it should. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
