[postgis-devel] ST_NumGeometries/ST_GeometryN

[Mark Cave-Ayland]

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.


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs