Question

Using Django 1.3 with PostgreSQL 9.0, I have a multi-step object creation function/view, where:

1. The main object is created (have tried both MyModel.objects.create() and manually using object.save() methods) and,
2. Then m2m relationships are setup (they must follow the main object creation so that said object has an id to relate to).

Some of those relationships may fail, or some other problem may arise, thus I need the entire function to behave atomically.

I’ve tried wrapping the function with the transaction.commit_on_success decorator, as well as tried using commit_manually (and setting the commit point at the end of the function); but neither works. That is, the main object is created and saved in the database, even when an exception is raised later on in the function. This leaves the database in an inconsistent state, to put it politely. So, how to debug this? I’ve seen similar questions, but they had to do with using MySQL, whereas this kind of broken transaction is not supposed to happen with Postgres. There were tickets on the Django Trac about this issue from years back, but they were supposedly fixed/resolved. Could any Djangonauts out there provide enlightenment please?

Answer 1

See this ticket: https://code.djangoproject.com/ticket/6669

I think for now you’ll just need to call transaction.rollback() explicitly when you get an IntegrityError