Changes between Initial Version and Version 12 of Ticket #22423


Ignore:
Timestamp:
Jan 29, 2019, 3:16:54 PM (5 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22423

    • Property Component Uncategorized → GIS
    • Property Triage Stage Unreviewed → Ready for checkin
    • Property Version 1.6 → master

  • Ticket #22423 – Description

    initial v12  
    1 Hi,
     1MySQL 5.6 and later implements spatial functions properly. (i.e., similar to PostGIS, mysql also supports `ST_Contains`, `ST_Within` and other `ST_` queries.) http://dev.mysql.com/doc/refman/5.6/en/functions-for-testing-spatial-relations-between-geometric-objects.html#function_st-contains
    22
    3 Starting from 5.6 version, mysql implemented spatial functions properly.
    4 (ie, similar to postgis, mysql also supports ST_Contains, ST_Within and other ST_ queries.)
    5 http://dev.mysql.com/doc/refman/5.6/en/functions-for-testing-spatial-relations-between-geometric-objects.html#function_st-contains
    6 
    7 Geodjango currently implements poly__contains and other queries for mysql as "MBRContains" instead of "Contains"
     3Geodjango currently implements `poly__contains` and other queries for mysql as "MBRContains" instead of "Contains"
    84https://docs.djangoproject.com/en/dev/ref/contrib/gis/geoquerysets/#std:fieldlookup-gis-contains
    95
    10 This needs to be fixed.
    11 related Ticket :
    12 
    13 https://code.djangoproject.com/ticket/13430
     6related Ticket: #13430
Back to Top