Refs #26112 -- Fixed aggregate GIS test on Oracle.

Made sure the test doesn't try to aggregate over MultiPolygonField and made
AreaField turn decimals into floats on the way from the DB.

Thanks Daniel Wiesmann, Jani Tiainen, and Tim Graham for review and discussion.
This commit is contained in:
Shai Berger 2016-01-26 00:50:46 +02:00 committed by Tim Graham
parent 75143fa13f
commit bb51dc902d
3 changed files with 17 additions and 2 deletions

View file

@ -353,7 +353,10 @@ Backwards incompatible changes in 1.10
Database backend API
--------------------
* ...
* GIS's ``AreaField`` uses an unspecified underlying numeric type that could in
practice be any numeric Python type. ``decimal.Decimal`` values retrieved
from the database are now converted to ``float`` to make it easier to combine
them with values used by the GIS libraries.
``select_related()`` prohibits non-relational fields for nested relations
-------------------------------------------------------------------------
@ -515,6 +518,10 @@ Miscellaneous
argument of the ``render_options()`` method is also removed, making
``selected_choices`` the first argument.
* On Oracle/GIS, the :class:`~django.contrib.gis.db.models.functions.Area`
aggregate function now returns a ``float`` instead of ``decimal.Decimal``.
(It's still wrapped in a measure of square meters.)
.. _deprecated-features-1.10:
Features deprecated in 1.10