Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#29307 closed Bug (fixed)

inspectdb generates Incorrect import paths for contrib.postgres fields

Reported by: Alasdair Nicol Owned by: Alasdair Nicol
Component: contrib.postgres Version: 2.0
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

The introspection rules for django.contrib.postgres fields incorrectly use django.contrib.postgresql.

https://github.com/django/django/blob/a599ae6018f748f66e774604d12989911ea09d33/django/contrib/postgres/apps.py#L20

As reported on Stack Overflow

Change History (5)

comment:1 Changed 2 years ago by Alasdair Nicol

Owner: changed from nobody to Alasdair Nicol
Status: newassigned

comment:2 Changed 2 years ago by Tim Graham

Component: Migrationscontrib.postgres
Severity: NormalRelease blocker
Summary: Incorrect introspection of django.contrib.postgres fields.inspectdb generates Incorrect import paths for contrib.postgres fields
Triage Stage: UnreviewedAccepted

comment:3 Changed 2 years ago by Alasdair Nicol

Has patch: set

comment:4 Changed 2 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: assignedclosed

In 65c44a5c:

Fixed #29307 -- Fixed inspectdb import paths for django.contrib.postgres fields.

Thanks erindy for the report.

comment:5 Changed 2 years ago by Tim Graham <timograham@…>

In 0eb71b85:

[2.0.x] Fixed #29307 -- Fixed inspectdb import paths for django.contrib.postgres fields.

Thanks erindy for the report.

Backport of 65c44a5c1d5412d402af19480e3c1c3e3e88893a from master

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