#12864 closed (fixed)
New users written to db_for_read
| Reported by: | Owned by: | Russell Keith-Magee | |
|---|---|---|---|
| Component: | contrib.auth | Version: | 1.2-beta |
| Severity: | Keywords: | multidb | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
We're experiencing a problem where new users are being inserted into the wrong database.
UserManager.create_user is applying the using filter, which is causing the db_for_read DB to be selected.
I've attached a patch that fixes this.
Thanks,
Haris
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | patch.diff added |
|---|
comment:1 by , 15 years ago
| milestone: | → 1.2 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [12488]) Fixed #12864 -- Corrected handling of new user creation when a multi-database router is in place. Thanks to haris@… for the report.