#28950: ArrayField.has_changed() returns True for unchanged fields
-------------------------------------+-------------------------------------
Reporter: tejinderss | Owner: vinay
| karanam
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.11
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"6a1957bb9887f8e0bb69d3d2b180a1414d38c1fc" 6a1957b]:
{{{
#!CommitTicketReference repository=""
revision="6a1957bb9887f8e0bb69d3d2b180a1414d38c1fc"
Fixed #28950 -- Fixed ArrayField.has_changed() for empty values.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28950#comment:7>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7862db189ece0372d3f589f9b17849ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
