> Hmmm, could be a double-click problem (the first request creates the > user between the check and create of the second request). I assume > make_random_password is not the problem ... > > Do you know which email/username causes the problem? Does it indeed > exist in the db ater the operation? Before?
Yes, I know email and after inspecting DB and access.log, I could not found any suspicious records. I double checked code, and could not found any potential problem. I contacted our hosting support, and try to solve it with them. I am satisfied that problems is some other place than my code :) Regards Michal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
