mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
spatial index #5022
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @collmomo on GitHub (Feb 24, 2016).
There's no mention of this in the documentation
CREATE SPATIAL INDEX sp_index ON geom (g);https://dev.mysql.com/doc/refman/5.7/en/creating-spatial-indexes.html
@Ocramius commented on GitHub (Feb 24, 2016):
Spatial indexes are engine-specific. We do not support them in core.
On Feb 24, 2016 03:50, "collmomo" notifications@github.com wrote:
@collmomo commented on GitHub (Feb 24, 2016):
I don't know what that means but I found the documentation here http://doctrine-orm.readthedocs.org/projects/doctrine-orm/en/latest/changelog/migration_2_5.html
@octaharon commented on GitHub (Oct 13, 2017):
But you support engine-specific "Options" still, don't you?
http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/annotations-reference.html#annref-index
So there's an obvious contradiction.
Also since "index" annotation has an undocumented "flags" property, it could be super easy to provide
Do you possibly have a recipe on how I can still have spatial indexes in my DB?
I'm not saying that you should support engine-specific things, but I don't see any real way of having a spatial index now without creating a shitlload of code which intercepts all of doctrine table-related events, circumvents sql generator and so on, while for the result I only need to add just one word to the query. That's completely bizarre