| | 51 | |
| | 52 | == When were the ST_* functions first added to match the SQL-MM-centric convention? == |
| | 53 | |
| | 54 | As of PostGIS 1.3 the renaming has been in effect, as the '''1.3 tag''' is the first appearance of ST_ prefixed functions in source:tags/1.3.0/lwgeom/lwpostgis.sql.in |
| | 55 | |
| | 56 | Therefore, non-prefixed functions (with ST_* equivalents) are '''deprecated''', and since the 1.3 release may not be maintained in the same way as the official ST_* functions, so '''don't expect them to work the same'''. |
| | 57 | |
| | 58 | For example only `ST_AsBinary` has been upgraded to work with the new `geography` type because `AsBinary` should not be being used anymore. |
| | 59 | |
| | 60 | Application developers should consider upgrading their code to use ST_* functions as soon as possible, therefore requiring at least PostGIS >=1.3. |
| | 61 | |
| | 62 | As Background: The official PostGIS documentation [http://postgis.refractions.net/docs/reference.html | states that] most functions have been renamed and "The non ST_ functions not listed in this documentation are deprecated and will be removed in a future release so STOP USING THEM." |
| | 63 | |
| | 64 | |
