#25226: ArrayField doesn't set the model attribute on the base_field instance
-------------------------------------+-------------------------------------
Reporter: Ion Scerbatiuc | Owner: Tim
| Graham <timograham@…>
Type: Bug | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: fixed
Keywords: arrayfield check- | Triage Stage:
framework | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
In [changeset:"2e55790838a75bf25a11115536dae57880cfccfb" 2e557908]:
{{{
#!CommitTicketReference repository=""
revision="2e55790838a75bf25a11115536dae57880cfccfb"
Refs #25226 -- Cloned ArrayField.base_field on deconstruction.
This prevents the base_field from sharing attributes with the one used
during migrations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25226#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.453adea8b17e869c3de4699a331b6f9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
