#852: psycopg.ProgrammingError exceptions leave the connection to the DB in an
unusable state
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution: wontfix
Keywords: |
---------------------------------------+------------------------------------
Comment (by [EMAIL PROTECTED]):
The workaround given earlier ("from django.core import db") no longer
works, as the db transaction code appears to have changed since it was
posted. How does one recover from a ProgrammingError now (without
reinitializing the whole db)?
--
Ticket URL: <http://code.djangoproject.com/ticket/852>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
