Opened 4 years ago

Closed 4 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 4 years ago.
From Github pull request #112

Download all attachments as: .zip

Change History (5)

comment:1 Changed 4 years ago by anonymous

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from 1.3-rc1 to 1.3

Changed 4 years ago by nosa_manuel

From Github pull request #112

comment:2 Changed 4 years ago by nosa_manuel

  • Has patch set
  • Version changed from 1.3 to 1.4-alpha-1

comment:3 Changed 4 years ago by claudep

  • Component changed from Uncategorized to GIS
  • Triage Stage changed from Unreviewed to Accepted
  • Type changed from Uncategorized to Bug

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

  • Resolution set to fixed
  • Status changed from new to closed

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