[postgis-users] ST_StartPoint fails with MultiLineString
Sandro Santilli
strk at keybit.net
Thu Nov 24 13:39:35 PST 2011
On Thu, Nov 24, 2011 at 05:06:20PM +0100, Jose Carlos Martinez wrote:
> Ok, I understand the strictness but what makes me confused if the
> mixed policy about standards.
>
> For example:
> PostGIS 1.5 -> ST_StartPoint and ST_Endoints with Multi types are
> working (against SQL/MM)
> PostGIS 2.0 -> ST_StartPoint and ST_Endoints with Multi types return
> null (folllow SQL/MM)
>
> PostGIS 1.5 -> ST_GeometryN (geom, 1) with simple types returns null
> (folllow SQL/MM)
> PostGIS 2.0 -> ST_GeometryN (geom, 1) with simple types are working
> (against SQL/MM)
>
> In some cases it follows the standards but in other cases it follows
> the usability.
It all started with 'ST_' enforcement.
Before that, we could be silly with 'ST_' names and smart w/out.
I guess nowadays it's not that worth being silly to follow
the standard ...
File tickets and fight for them !
--strk;
() Free GIS & Flash consultant/developer
/\ http://strk.keybit.net/services.html
More information about the postgis-users
mailing list