Geometry types and optimization
I've been playing around with MySQL's spatial extensions for a bit and noticed it is possible to save any type of subclass in a GEOMETRY column, while there are specific column/geometry types like POINT, LINESTRING and POLYGON (and some collections).
My question: does a more common column type impact optimization/speed in any way? Would a more explicit column (POINT for storing points, etc) be faster?
Thanks,
Bas
Subject
Views
Written By
Posted
Geometry types and optimization
5402
January 30, 2008 07:53AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.