Opened 8 years ago

Closed 7 years ago

#17687 closed Bug (fixed)

LayerMapping ignores database routers

Reported by: nosamanuel@… Owned by: nobody
Component: GIS Version: 1.4-alpha-1
Severity: Normal Keywords: gis router multidb
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


The LayerMapping class from contrib.gis currently supports multiple databases via a using argument that defaults to DEFAULT_DB_ALIAS. This fails when mapping a model that is routed to a non-default database.

Attachments (1)

pull-112.patch (4.2 KB) - added by nosa_manuel 8 years ago.
From Github pull request #112

Download all attachments as: .zip

Change History (5)

comment:1 Changed 8 years ago by anonymous

Version: 1.3-rc11.3

Changed 8 years ago by nosa_manuel

Attachment: pull-112.patch added

From Github pull request #112

comment:2 Changed 8 years ago by nosa_manuel

Has patch: set
Version: 1.31.4-alpha-1

comment:3 Changed 8 years ago by Claude Paroz

Component: UncategorizedGIS
Triage Stage: UnreviewedAccepted
Type: UncategorizedBug

comment:4 Changed 7 years ago by Claude Paroz <claude@…>

Resolution: fixed
Status: newclosed

In 7e32dab3a64570c67993d38b5bc25c9bd1f7455e:

Fixed #17687 -- Made LayerMapping router-aware

Thanks nosamanuel@… for the report and the initial patch.

Note: See TracTickets for help on using tickets.
Back to Top