On 23 May 2012 00:30, akaariai <akaar...@gmail.com> wrote: > On May 22, 11:49 pm, Hanne Moa <hanne....@gmail.com> wrote: >> I upgraded python to 2.6.8 today from an earlier 2.6, what an >> adventure! So much bizarre happenings so many places. > > Please provide these three things for further debugging: > - the exact Python code you try in the shell (including a real > username). > - the SQL that generates (when not working). > - what does happen when you try to run that SQL in manage.py dbshell > (you might need to add quotes to the parameters)
Problem solved. Exact lookups worked only intermittently in the database as well. Turns out the index on usernames was hosed. I remade it... alter table auth_user drop constraint auth_user_username_key; alter table auth_user add constraint auth_user_username_key UNIQUE (username); and now it works. For a little while it was possible to make duplicate users though (!) This calls for champagne, I've never seen an error in the database that failed so spectacularly silently before =D HM -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
