> No idea what's going on. However, you should be able to test this. You > now the queryset that is causing the problem, so run it manually (e.g. > via "manage.py shell") on your dev system and see what happens. Make > sure to replace one of the inputs with something that cannot > possibly be > in the database, which will replicate the problem.
I tried this, opening two interpreter sessions and evaluating a Picture queryset in one while a new Picture was being saved in the other, but got no errors, either with the new 404 enabled code, or what I was running before. As far as bare querysets go, this is exactly the setup that was causing problems before. I'm ready to chalk this up to an Act of God... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
