#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 anonymous):
Replying to [comment:1 [EMAIL PROTECTED]:
> The problem you see is not directly caused by the isolation level, but
by the fact that postgresql is not able to continue a transaction once a
statement has failed. I consider ticket #3460 the wrong solution, since it
basically turns off all transaction support.
>
> Your second block is the better solution.
>
> I close this ticket as a duplicate, though.
#3460 turns off transaction by default, which is correct. You still get
transaction if you explicitly use them (or perhaps I am confusing this
with my Twisted patches since they had the same problem). You want
singleton queries not inside BEGIN/END/COMMIT pairs, but you want multiple
INSERT or DELETE queries inside the pairs. Before the patch you get
BEGIN/END/COMMIT pairs on every query no matter what, which is quite
inefficient if you have lots of simple selects (which is 80% of what most
django apps do).
--
Ticket URL: <http://code.djangoproject.com/ticket/5043#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
