Changes between Initial Version and Version 1 of Ticket #33638, comment 1


Ignore:
Timestamp:
Apr 13, 2022, 3:04:51 AM (3 years ago)
Author:
Mariusz Felisiak

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33638, comment 1

    initial v1  
    1 I was able to reproduce this issue, however using geography type is really limited on PostGIS (see [https://docs.djangoproject.com/en/stable/ref/contrib/gis/model-api/#geography-type-1 docs]) and `__bboverlaps` is not an option in the general case. I wonder how we could improve this, I can imagine two options:
     1Tentatively accepted for future investigation. I was able to reproduce this issue, however using geography type is really limited on PostGIS (see [https://docs.djangoproject.com/en/stable/ref/contrib/gis/model-api/#geography-type-1 docs]) and `__bboverlaps` is not an option in the general case. I wonder how we could improve this, I can imagine two options:
    22- raise a system warning when `unique` is used with `geography` and skip these fields in unique checks,
    33- cast `geography` fields to a `geometry` type in the query.
Back to Top