#5043: Postgresql transaction error handling is different
-------------------------------------------------+--------------------------
Reporter: Nis Jørgensen <[EMAIL PROTECTED]> | Owner:
adrian
Status: closed | Component:
Database wrapper
Version: SVN | Resolution:
duplicate
Keywords: | Stage:
Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------------------+--------------------------
Comment (by Nis Jørgensen <[EMAIL PROTECTED]>):
I disagree that this is a duplicate of #3460. This bug is about the
behavior of django when in a transaction. 3460 is about whether django is,
bu default, in a transaction. So I am reopening the ticket.
I do not have an opinion on whether 3460 should be fixed or not - I am not
really sure about the implications of it.
Nis
--
Ticket URL: <http://code.djangoproject.com/ticket/5043#comment:4>
Django Code <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---
