Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 1caa483914edf851137b3c1e39f4364772bd46c9
      
https://github.com/django/django/commit/1caa483914edf851137b3c1e39f4364772bd46c9
  Author: Anssi Kääriäinen <[email protected]>
  Date:   2012-12-16 (Sun, 16 Dec 2012)

  Changed paths:
    M django/db/backends/__init__.py

  Log Message:
  -----------
  [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



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to