#19197: BaseDatabaseOperations: convert_values raise error on None data type
conversions
-------------------------------------+-------------------------------------
Reporter: maxi | Owner:
Type: Bug | maxirobaina@…
Component: Database layer | Status: closed
(models, ORM) | Version: 1.4
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 Anssi Kääriäinen <akaariai@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"1caa483914edf851137b3c1e39f4364772bd46c9"]:
{{{
#!CommitTicketReference repository=""
revision="1caa483914edf851137b3c1e39f4364772bd46c9"
[1.5.x] Fixed #19197 -- fixed convert_values() for nullable numeric fields
Cleaned up the implementation of base convert_values() a little, and
made sure it accepts None as a value for numeric fields.
There are no tests attached. The reason is that not all of the
convert_values() accept None as a value for numeric fields (for example
sqlite3.convert_values()).
The reason the base convert_values() needs to accept None is that this
situation might arise in custom compilers for 3rd party backends. It
is easy to keep the convert_values() working, so lets do that.
Backpatch of 12a96bfa263d514884ef11009913b2f8bb163472
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19197#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
