on PostGIS:
{{{
In [1]: from test_app.models import City
In [2]: from django.contrib.gis.geos import Point
In [3]: c = City.objects.create(point=Point(1, 1, srid=3857))
In [7]: c.refresh_from_db()
In [9]: print(c.point)
SRID=4326;POINT (8.983152841195214e-06 8.983152840993819e-06)
}}}
on MySQL:
{{{
In [1]: from test_app.models import City
In [2]: from django.contrib.gis.geos import Point
In [3]: c = City.objects.create(point=Point(1, 1, srid=3857))
In [4]: c.refresh_from_db()
In [5]: print(c.point)
SRID=4326;POINT (1 1)
}}}
I think that more appropriate behavior is to raise some error.
--
Ticket URL: <https://code.djangoproject.com/ticket/27964>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => Sergey Fedoseev
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/27964#comment:1>
* stage: Unreviewed => Accepted
* type: Bug => Cleanup/optimization
Comment:
Probably a mention in the backwards incompatible changes section of the
release notes would be a good idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/27964#comment:2>
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/8676 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27964#comment:3>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"44a7b98abbec02f1a4f35662040f602fd616d0cd" 44a7b98a]:
{{{
#!CommitTicketReference repository=""
revision="44a7b98abbec02f1a4f35662040f602fd616d0cd"
Fixed #27964 -- Made MySQL backend raise exception if spatial
transformation is needed for query.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27964#comment:4>