#20103: None no longer matches zero-length string on CharField
-------------------------------+--------------------
Reporter: simon29 | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------
I've just updated from 1.5 stable to latest commit
aaec4f2bd8a63b3dceebad7804c5897e7874833d.
`Model.objects.filter(mycharfield=None)` ''used to'' return instances
where mycharfield is actually a zero-length string.
Now, it seems I need to explicitly specify
`Model.objects.filter(mycharfield='')`
Minor change, but the implications could be pretty severe for some apps.
Suggest either reverting to previous behaviour or updating the "backwards
incompatible changes" list.
--
Ticket URL: <https://code.djangoproject.com/ticket/20103>
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.
For more options, visit https://groups.google.com/groups/opt_out.
