From 44a7b98abbec02f1a4f35662040f602fd616d0cd Mon Sep 17 00:00:00 2001 From: Sergey Fedoseev Date: Mon, 26 Jun 2017 16:42:31 +0500 Subject: Fixed #27964 -- Made MySQL backend raise exception if spatial transformation is needed for query. --- docs/ref/contrib/gis/tutorial.txt | 2 ++ docs/releases/2.0.txt | 4 ++++ 2 files changed, 6 insertions(+) (limited to 'docs') diff --git a/docs/ref/contrib/gis/tutorial.txt b/docs/ref/contrib/gis/tutorial.txt index 1fb73c9c7f..7ab3c81415 100644 --- a/docs/ref/contrib/gis/tutorial.txt +++ b/docs/ref/contrib/gis/tutorial.txt @@ -610,6 +610,8 @@ of a queryset:: The ``contains`` and ``intersects`` lookups are just a subset of the available queries -- the :doc:`db-api` documentation has more. +.. _automatic-spatial-transformations: + Automatic Spatial Transformations --------------------------------- When doing spatial queries, GeoDjango automatically transforms diff --git a/docs/releases/2.0.txt b/docs/releases/2.0.txt index 37bfb48d89..cd1970f08f 100644 --- a/docs/releases/2.0.txt +++ b/docs/releases/2.0.txt @@ -472,6 +472,10 @@ Miscellaneous option. Add this to your existing migrations or accept an auto-generated migration for fields that use it. +* Performing queries that require :ref:`automatic spatial transformations + ` now raises ``NotImplementedError`` + on MySQL instead of silently using non-transformed geometries. + .. _deprecated-features-2.0: Features deprecated in 2.0 -- cgit v1.3