[postgis-devel] Non-C functionality

[Mark Cave-Ayland]

Paul Ramsey wrote:

> This raises an issue of policy which our "API stable" promise makes
> perhaps worth articulating: functionality should be implemented
> primarily in the C library. Otherwise we're going to have this issue,
> of "bugs in the SQL" which cannot be solved by a library drop-in, and
> that require extra DBA attention.
> 
> If the goal of "no SQL upgrades" is paramount, then moving more code
> into C makes sense.
> 
> P.

Yeah, I think we should definitely err towards C wherever possible (I 
see you added some suitable LWGEOM_hasz/m in a previous commit), just 
for performance reasons if nothing else.


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