[postgis-devel] Function Removal

[Paul Ramsey]

SQL/MM believes in having All The Variants.


CREATE CONSTRUCTOR METHOD ST_Point (awkb BINARY LARGE OBJECT(ST_MaxGeometryAsBinary)) RETURNS ST_Point

CREATE CONSTRUCTOR METHOD ST_Point (awkb BINARY LARGE OBJECT(ST_MaxGeometryAsBinary), ansrid INTEGER) RETURNS ST_Point

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION) RETURNS ST_Point 

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION, ansrid INTEGER) RETURNS ST_Point 

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION, zcoord DOUBLE PRECISION) RETURNS ST_Point

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION, zcoord DOUBLE PRECISION, ansrid INTEGER) RETURNS ST_Point FOR ST_Point BEGIN

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION, zcoord DOUBLE PRECISION, mcoord DOUBLE PRECISION) RETURNS ST_Point

CREATE CONSTRUCTOR METHOD ST_Point (xcoord DOUBLE PRECISION, ycoord DOUBLE PRECISION, zcoord DOUBLE PRECISION, mcoord DOUBLE PRECISION, ansrid INTEGER) RETURNS ST_Point


> On Dec 16, 2020, at 1:42 PM, Sandro Santilli <strk at kbt.io> wrote:
> 
> On Wed, Dec 16, 2020 at 04:22:48PM -0500, Regina Obe wrote:
> 
>> Add SRID to ST_Point(x,y) -- you can keep existing or overload.  Overloading
>> with another that has srid not optional would be more backward compatible.
>> That's the one I use and that most people should be using as it's shorter to
>> type and name wise is listed in SQL/MM.
> 
> I belive SQL/MM knows about Z as well
> Better be strict on SQL/MM definitions when touching those
> signatures.
> 
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel