On Mon, 2009-03-23 at 12:11 -0700, Peter Sheats wrote: [...] > The error I was getting before was just a "connection already closed > error" until I changed the following in wsgi.py line 235-248:
Well, that's really the more important issue, then. Why is the connection already closed when Django expects it to already be opened. You need to investigate that problem a bit more, I think. It's related to the error you get when you change things (since the attempt to close off the savepoint will be causing a new connection to be opened, which will have a different transaction status, etc -- it's all a consequence of the first problem). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
