Timeline for Is the ST_ prefix appropriate for functions not included in SQL/MM Part 3?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2019 at 12:27 | vote | accept | Brideau | ||
| Jan 18, 2019 at 8:21 | answer | added | Evan Carroll | timeline score: 1 | |
| Nov 14, 2018 at 23:03 | comment | added | Brideau | No, that question is about what ST_ means, while this is about when it is appropriate to use it. | |
| Nov 14, 2018 at 17:21 | comment | added | Ian Turton | possible duplicate of gis.stackexchange.com/questions/286808/… | |
| May 4, 2018 at 19:43 | history | reopened |
John Powell Brideau lynxlynxlynx Andre Silva xunilk |
||
| May 4, 2018 at 14:48 | comment | added | Brideau | Whether or not SQL/MM can or cannot force a developer to do something isn't the question I'm asking. I'm asking about what the standard itself recommends. The standard is 1500 pages long, and I haven't read every line of it, so I'm asking the community here - some of whom help to write it and related standards - what is recommended, or perhaps whether it defers these decisions to another standard or explicitly chose not to address this. These are fact-based requests. | |
| May 4, 2018 at 14:31 | comment | added | user30184 | For my mind it is opinion based. SQL/MM standard cannot deny developers from creating their own functions with ST_ prefix if they want, even non-spatial functions. However, developers may deside to do it in another way. As a comparison SpatiaLite has many spatial but non-SQL/MM functions which have ST_ synonyms, some others which do not have gaia-gis.it/gaia-sins/spatialite-sql-latest.html. | |
| May 4, 2018 at 14:12 | review | Reopen votes | |||
| May 4, 2018 at 19:43 | |||||
| May 4, 2018 at 13:51 | comment | added | John Powell | Apologies, I have just re-read your question and there is indeed a clear, non-opinion based question in there. My 2c is that if it is explicitly spatial, it gets an ST_, irrespective of whether it is in the standards or not. I have cast a reopen vote. | |
| May 4, 2018 at 13:47 | history | edited | Brideau | CC BY-SA 4.0 |
added 274 characters in body
|
| May 4, 2018 at 13:41 | comment | added | Brideau | I don't understand why my question was just put on hold for being "opinion based." My question is explicitly about whether it is opinion-based, or if there is some aspect of the standard I'm overlooking that makes this decision fact-based. | |
| May 4, 2018 at 12:30 | history | closed |
user30184 nmtoken aldo_tapia John Powell Jochen Schwarze |
Opinion-based | |
| May 4, 2018 at 11:11 | comment | added | John Powell | I think it is a fair question, but, essentially comes down to a matter of opinion. I expect all functions that are manifestly spatial, ie, they operate on a vector, raster, topology, 3D surface, etc, to take the prefix ST_. It had never occcured to me to ask if this was appropriate usage based on whether it was in a spec or not. While interoperability is important and desirable, I certainly wouldn't want Postgis held back by only implementing functions in the SQL/MM spec. And I think using some other prefix would cause lots of confusion. | |
| May 4, 2018 at 6:14 | review | Close votes | |||
| May 4, 2018 at 12:30 | |||||
| May 4, 2018 at 1:21 | history | tweeted | twitter.com/StackGIS/status/992212507237462016 | ||
| May 3, 2018 at 23:55 | history | edited | Brideau | CC BY-SA 4.0 |
added 14 characters in body
|
| May 3, 2018 at 21:26 | history | asked | Brideau | CC BY-SA 4.0 |