Would a MBR function query against an indexed column with geometry type containing points and polygons (GeomCollection type) be slower than a MBR function against an indexed column with a polygon type?
My programmer instincts tell me that it would be slower and I should use the most descriptive spatial type I can.
Edit: After reading Denis's answer, the real question is:
In MySQL "does an indexed column with geometry type containing points and polygons actually contain the latter or are they reduced to a MBR?"
I'm risking an answer here, without being sure on the MySQL front...
But in Postgres, geometry types indexed using GIST will usually be indexed as boxes, a.k.a. MBR, irrespective of what whether they're circles, polygones, etc.
So the real question might be better rephrased as: "does an indexed column with geometry type containing points and polygons actually contain the latter or are they reduced to a MBR?"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With