#15117: get_or_create() raises "DatabaseError: no such savepoint" instead of IntegrityError (PostgreSQL) -------------------------------------+------------------------------------- Reporter: akaihola | Owner: aaugustin Type: Bug | Status: assigned Component: Database layer | Version: master (models, ORM) | Resolution: Severity: Normal | Triage Stage: Accepted Keywords: | Needs documentation: 0 Has patch: 0 | Patch needs improvement: 0 Needs tests: 0 | UI/UX: 0 Easy pickings: 0 | -------------------------------------+-------------------------------------
Comment (by aaugustin): I just introduced `django.db.transaction.atomic` that precisely designed for this use case. It uses "release savepoint" instead of "commit", which allows rolling back to the savepoint if necessary. -- Ticket URL: <https://code.djangoproject.com/ticket/15117#comment:13> Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.