[postgis-devel] ST_NumGeometries/ST_GeometryN

[strk]

On Fri, Mar 12, 2010 at 01:05:32PM +0000, Mark Cave-Ayland wrote:
> strk wrote:
> 
> >Current behaviour of NumGeometries/GeometryN
> >is to always return NULL if the input is a single
> >geometry.
> >
> >JTS/GEOS moved to support single geoms from similar
> >functions already, returning 1 from NumGeometries
> >and the input on GeometryN(1).
> >
> >As for collections, GeometryN(<out_of_range_index>)
> >should still retur null.
> >
> >Is everyone fine in also changing postgis interface
> >to do that ?
> 
> Hi strk,
> 
> Sounds like a sensible change to me, but let's keep it in trunk.

Since we're at it, should the function definition also change
to reference an ST_GeometryN and ST_NumGeometries rather than
the current LWGEOM_geometryn_collection/LWGEOM_numgeometries_collection ?

--strk;

  ()   Free GIS & Flash consultant/developer
  /\   http://strk.keybit.net/services.html