#23761: Mysql validator crashes with None db_type return. - Backport of master
fix
to 1.7
-------------------------------+---------------------------
Reporter: adepue | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
Severity: Normal | Keywords: mysql db_type
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+---------------------------
A fix was made in August in master:
https://github.com/django/django/commit/e9103402c0fa873aea58a6a11dba510cd308cb84#diff-14
The fix contains a lot more than is needed for this specific issue,
however the specific changes to django/db/backends/mysql/validation.py
would be great to have in Django 1.7
The issue is that if you create a custom field that returns None for
db_type(), then it causes crashes due to dereference None to check the
startswith().
This worked fine in < Django 1.7 and works fine in upstream.
--
Ticket URL: <https://code.djangoproject.com/ticket/23761>
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/049.8b5a234facc8ce678fe22db0a6ecfda7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
