Timeline for Is it ok to group by geometry in PostGIS?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Sep 15, 2017 at 17:28 | history | suggested | chicks | CC BY-SA 3.0 |
better title
|
Sep 15, 2017 at 17:13 | review | Suggested edits | |||
S Sep 15, 2017 at 17:28 | |||||
Sep 11, 2017 at 13:02 | vote | accept | Inactivated Account | ||
Sep 11, 2017 at 7:22 | history | tweeted | twitter.com/StackGIS/status/907142179851788288 | ||
Sep 10, 2017 at 23:59 | answer | added | dbaston | timeline score: 25 | |
Sep 10, 2017 at 23:38 | comment | added | Inactivated Account | It allows me to not have to wrap the count query as a sub-query to join on the nbhd_id - if it increases runtime to group by geometry, then that is a possible reason to NOT do this, wouldn't you say? | |
Sep 10, 2017 at 23:14 | comment | added | Vince |
What does the GROUP BY gain you? Isn't it joinable by a unique key of nbhd_id ? You are making the sort wider, which increases runtime, possibly by more than a subsequent join.
|
|
Sep 10, 2017 at 21:57 | history | asked | Inactivated Account | CC BY-SA 3.0 |