TransactionManagementError with ATOMIC_REQUESTS enabled

[roelwivion]

While using your app I noticed TransactionManagementError errors occurs when logging in with the ATOMIC_REQUESTS setting set to True. (Python: 2.7.3, Django: 1.6.4)

The traceback "refers to /user_sessions/backends/db", line 77 "with transaction.commit_on_success(using)". I believe this line should be replaced with atomic transaction.atomic(using):.
According to the Django docs:

"Starting with Django 1.6, atomic() is the only supported API for defining a transaction. Unlike the deprecated APIs, it’s nestable and always guarantees atomicity"

Thank you for this project, it's really handy.

[Bouke]

Hi @roelwivion, thanks for the report. I had some problems replicating your issue at first, but I finally managed to reproduce it. However I cannot reproduce the error in a unit test, so hopefully it will continue working in the future. To make sure it does, I enabled atomic requests in the example app.