[postgis-devel] Deprecation Warnings

[David William Bitner]

+1, I like Cake.

On Fri, Jan 23, 2009 at 2:59 PM, Kevin Neufeld <kneufeld at refractions.net>wrote:

> What if we deprecate the functions as you suggest (and eventually remove
> them), but provide a sql script that will reinstate them as wrappers to the
> ST_* methods.  That way, folks can have their cake and eat it too ...
> upgrade to the latest version without breaking their apps.
>
> -- Kevin
>
>
> Paul Ramsey wrote:
>
>> Could we use the function creation option
>>
>> SET configuration_parameter { TO value | = value | FROM CURRENT }
>>
>> to, for example, set postgis_deprecated to true?
>> Then in the function, we could warn on deprecation. So the same
>> backend to intersects() could be used by several function names, but
>> only some would raise deprecation warnings.
>>
>> Or do we want to continue our gentle regime of letting the old names
>> live in quite obscurity?
>>
>> P.
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>



-- 
************************************
David William Bitner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20090123/43ee2eca/attachment.html>