Thanks. I solved the problem. I added transaction.rollback() to one of the exceptions. Thanks
On Feb 1, 2:27 pm, Shawn Milochik <sh...@milochik.com> wrote: > Do you have any messages coming from prior to that? The error you're > receiving comes when something else has blown up with your database > transaction, and then your code tries to execute something else against the > database while your transaction is already 'broken.' So, the problem is > probably not with that print statement, but with whatever was tried against > the database before that. > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
