Skip to main content

Timeline for && vs ST_Intersects performance

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
S Mar 26 at 11:37 history suggested adrien.ludwig CC BY-SA 4.0
Fix multiple typos
Mar 26 at 8:03 review Suggested edits
S Mar 26 at 11:37
Nov 25, 2017 at 8:19 history edited Evan Carroll CC BY-SA 3.0
added 255 characters in body
Nov 25, 2017 at 7:40 history edited Evan Carroll CC BY-SA 3.0
added 8 characters in body
Nov 25, 2017 at 0:25 history edited Evan Carroll CC BY-SA 3.0
added 6 characters in body
Nov 24, 2017 at 23:54 history edited Evan Carroll CC BY-SA 3.0
added 442 characters in body
Nov 24, 2017 at 23:00 history edited Evan Carroll CC BY-SA 3.0
added 179 characters in body
Nov 24, 2017 at 21:58 comment added Evan Carroll @yurtesen see the update.
Nov 24, 2017 at 21:58 history edited Evan Carroll CC BY-SA 3.0
added 74 characters in body
Nov 24, 2017 at 20:04 comment added yurtesen When I said "does same thing" what I meant was the result set will be mostly same when one is looking at a point inside an envelope because point overlaps with area of envelope? ( Perhaps not 100% same results since I read the ST_Intersects still returns true when point is very close to the boundary for geography ). But for example POINT(1 1) intersects POLYGON((0 0, 1 1, 2 2, 3 3, 0 0)) returns true because point is inside polygon. My problem now is that due to some reasons Doctrine DQL does not accept && and I need to use an ST_ function... I need to know which one is more efficient ...
Nov 24, 2017 at 19:35 vote accept yurtesen
Nov 24, 2017 at 16:41 history edited Evan Carroll CC BY-SA 3.0
added 653 characters in body
Nov 24, 2017 at 16:29 history answered Evan Carroll CC BY-SA 3.0