On Mon, 2008-02-18 at 00:54 +0800, Eric Abrahamsen wrote: > > > > So it seems like there's something else going wrong. Does the same > > error > > occur if you try to pull an image from the database that is guaranteed > > not to exist (so there's no question of it being a race condition)? If > > so, that just means your error handling for missing items needs > > improvement. > > As soon as I tried this I realized that I wasn't handling 404 > possibilities, so they were resulting in server errors. I added a > get_object_or_404 method, a 404 template, and then tried the whole > thing again, and got no proxy errors. I don't understand why that > should be - the view that was giving me errors was not retrieving a > single Picture directly, simply a queryset of Pictures that that one > Picture would have belonged to, had it been safely in the database. > Does this make sense at all?
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. Malcolm -- Honk if you love peace and quiet. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
