[5.5] Blueprint Geo Spatial index #21070
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR continues #21056 and introduces spatial indexes in your migrations with the
spatialIndex
blueprint method.Note: At this moment I've implemented only MySQL grammar
SPATIAL INDEX
support.Example:
You can drop it using default
$table->dropIndex('column_name')
command.MySQL
Note about spatial indexes from the MySQL documentation:
MySQL
SPATIAL INDEX
creates an R-tree index. For storage engines that support nonspatial indexing of spatial columns, the engine creates a B-tree index. A B-tree index on spatial values is useful for exact-value lookups, but not for range scans.MyISAM
andInnoDB
tables. SpecifyingSPATIAL INDEX
for other storage engines results in an error.PostgreSQL
Accordingly to PostGIS Spatial Indexing article: