Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#26101 closed Bug (fixed)

RangeField.base_field has no model attribute

Reported by: Bertrand Bordage Owned by: Anna Schneider
Component: contrib.postgres Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Like it was in #25867 for ArrayField, RangeField and its subclasses do not have the model attribute in their base_field.

I didn’t find any use case where it triggers a bug as blocking as in #25867, however this is problematic when doing advanced introspection on the ORM, as I faced.
A similar solution as the one for #25867 should work.

Change History (5)

comment:1 by Simon Charette, 10 years ago

Triage Stage: Unreviewed → Accepted
Version: 1.9 → master

comment:2 by Anna Schneider, 10 years ago

Has patch: set
Owner: set to Anna Schneider
Status: new → assigned

comment:3 by Markus Holtermann, 10 years ago

Triage Stage: Accepted → Ready for checkin

comment:4 by Markus Holtermann <info@…>, 10 years ago

Resolution: → fixed
Status: assigned → closed

In b28c605:

Fixed #26101 -- Allowed introspection of base_field.model in RangeField

Used the same test and fix as in #25867.
This required initializing base_field in RangeField.init,
not when setting the attribute.

comment:5 by Bertrand Bordage, 10 years ago

Thanks a lot, Anna & Markus! :)

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