[postgis-devel] Should we start using default args now?

[Paul Ramsey]

We can include DROP IF EXISTS at the front of the upgrade scripts
(already do that do some extent) to clean out non-defaulted
pre-existing functions.
P.

On Mon, May 16, 2011 at 11:04 PM, Paragon Corporation <lr at pcorp.us> wrote:
> No CREATE OR REPLACE would not  replace them.  We would have to drop them.
>
> I was thinking about just new functions like the 100 some odd Bborie just
> loaded on us :)
>
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Sandro
> Santilli
> Sent: Tuesday, May 17, 2011 2:01 AM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] Should we start using default args now?
>
> On Tue, May 17, 2011 at 01:01:13AM -0400, Paragon Corporation wrote:
>> Now that Bborie has unleashed his load of functions; I'm not
>> complaining, I did ask for it :)
>>
>> I was wondering if maybe we should start using default arguments at
>> least for raster.  Now that our minimum is 8.4 for PostGIS 2.0, this
>> is now an option.  Does it make sense?
>
> If 8.4 supports them, I'm for it. Surely for new functions.
> Old functions might need more verifications (does CREATE OR REPLACE replace
> them ?).
>
> --strk;
>
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
> _______________________________________________
> 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
>