Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7k
Fix set_rollback on @transaction.non_atomic_requests.#3016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
xordoquy commentedJun 8, 2015
Thanks for the pull request. |
xordoquy commentedJun 8, 2015
The provided test is already working against the current master (without your fix being included). |
hellysmile commentedJun 8, 2015
@xordoquy Here is runnig app With this code |
hellysmile commentedJun 8, 2015
Hey, In addition, @xordoquy can You try now without checking It was really hard to figure out this Django test internals... |
xordoquy commentedJun 8, 2015
@hellysmile ace ! |
Fix set_rollback on @transaction.non_atomic_requests.
xordoquy commentedJun 8, 2015
Thanks for the PR ! |
set_rollback()checks only
ATOMIC_REQUESTvalue, but it can be turned off per view by@transaction.non_atomic_requestsAttempt to rollback without atomic block raises
https://github.com/django/django/blob/06dc6759d85c6c24b599de07cea47387d3dc2cf9/django/db/backends/base/base.py#L361
Really critical, due
http404for every@transaction.non_atomic_requests