#24034 closed Bug (fixed)
ArrayField.deconstruct always overwrites path
Reported by: | Jernej Kos | Owned by: | |
---|---|---|---|
Component: | contrib.postgres | Version: | dev |
Severity: | Normal | 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 new django.contrib.postgres.fields.ArrayField
seems to always overwrite the path
element in the returned deconstruct
tuple instead of using the path generated by Field
base class. This causes the path to be wrong in ArrayField subclasses and requires it to be explicitly set instead of just using the one generated by the Field
base class.
It would be better to change it to something like in the Field
class, where the current value of the path
is checked first before rewriting the path into a shorter form.
Change History (3)
comment:1 by , 10 years ago
Has patch: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Bug |
comment:2 by , 10 years ago
Owner: | set to |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In 7c50e7eeccd4b4581542547f5ddb603bbd62a725: