[postgis-devel] Compatibility between postgis 2 & mapserver

[Paragon Corporation]

Andrea,

Yes we really want to in order to get rid of otherwise dead code in our code
base which makes it hard to find non-dead code and otherwise
prevent users from getting confused by thousands of redundant functions.

We have a legacy_compatibility_layer.sql which users who can't upgrade their
tools can use.  It has what we think most legacy tools are using.  I know
GeomFromText/Asbinary/SetSRID is in that file.

I'll double check on force_collection and force_2d to make sure I have those
in that file.  If thisngs sitll don't work you can go for the full monty --
legacy.sql which reinstalls 500 someodd redundant functions we removed.

Thanks,
Regina

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net 
> [mailto:postgis-devel-bounces at postgis.refractions.net] On 
> Behalf Of Martin Spott
> Sent: Saturday, January 07, 2012 7:58 PM
> To: postgis-devel at postgis.refractions.net
> Subject: Re: [postgis-devel] Compatibility between postgis 2 
> & mapserver
> 
> Andrea Peri wrote:
> 
> > But before ask to the ML of MapServer I need to know if the 
> remove of 
> > geomfromtext() is wanted or not in postgis 2.0
> 
>   geomfromtext -> ST_GeomFromText  in Postgis 2.x
> 
> Everyting's in "mappostgis.c", there are just four lines to 
> edit (at least in MS 5.6.5) containing:
> 
>   GeomFromText -> ST_GeomFromText
>   AsBinary -> ST_AsBinary
>   force_collection -> ST_Force_Collection
>   force_2d -> ST_Force_2D
> 
> Cheers,
> 	Martin.
> --
>  Unix _IS_ user friendly - it's just selective about who its 
> friends are !
> --------------------------------------------------------------
> ------------
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>