Examine this statement, which executes successfully:
You want to improve the performance of this query:
Which change enables the query to succeed while accessing fewer rows?
Examine this statement, which executes successfully:
You want to improve the performance of this query:
Which change enables the query to succeed while accessing fewer rows?
To improve the performance of a query that filters based on a range of integer values, adding an index on the column involved in the WHERE clause is effective. In this case, adding an index on the Population column will enable the database to locate the rows corresponding to the specified range more efficiently. A SPATIAL INDEX is not appropriate here because Population is an integer type and spatial indexes are designed for geometrical data types. Thus, the correct change to improve query performance is to add an index on the Population column.
agree with C. running command line option B generated error 1687: A SPATIAL index may only contain a geometrical type column.
Answer should be C
Answer must be C, int is not spatial column
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. The optimizer can use spatial indexes defined on columns that are SRID-restricted. So answer is B.
Answer C
population is INT
Correct answer should be C . You can't add a spartial index on non-geo data types