#23089 closed Bug (fixed)
manage.py flush --database=custom uses wrong transaction
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Management commands) | Version: | 1.6 |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
This is a regression from 1.5
If a non-default database is passed to flush management command, it still starts a transaction on 'default' database. This can be easily seen by setting 'default' database settings to an empty dictionary.
This is still in branches 1.6 and 1.7, but apparently fixed in master with commit 753a22a6352638b7df55176584795ac8c5d4232c
Change History (6)
comment:1 by , 10 years ago
Component: | Uncategorized → Core (Management commands) |
---|---|
Easy pickings: | unset |
Has patch: | set |
Severity: | Normal → Release blocker |
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Bug |
comment:2 by , 10 years ago
Indeed, the regression was introduced in ba5138b1c0253fcf390b7509ad7b954117b3be88, which replaces transaction.commit/rollback_unless_managed(using=db)
with transaction.commit_on_success_unless_managed()
.
I should have backported the fix. At the time it seemed minor and I didn't check whether it was a regression.
Since the biggest part is the release notes, I would really appreciate if you can take care of that. Of course, if you have other priorities, I'll fix my own mess ;-)
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Aymeric, can we just add 1.6.6 release notes and backport that commit?