Re: Function with default value not replacing old definition of the function - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Function with default value not replacing old definition of the function
Date
Msg-id 1A12792B-109A-4E3F-BF21-6F68599D73CB@hi-media.com
Whole thread Raw
In response to Re: Function with default value not replacing old definition of the function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Function with default value not replacing old definition of the function
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Le 11 déc. 08 à 16:22, Tom Lane a écrit :
> Yeah, we already bit this bullet with variadic functions --- if you
> have
>     myfunc(int, float)
>     myfunc(int, variadic float[])
> then it's ambiguous which one should be used for call "myfunc(11,
> 12.5)".
> The sanest answer I can see is "so, don't do that".


Is there any warning level message at CREATE FUNCTION time for the
user/dba to know he's doing something... border line, almost shooting
himself in the foot?

I'd really welcome such an error message as a reminder to consider
seriously such a choice, which would not be though out in lot of cases
I suppose.

Regards,
- --
dim




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAklBaQoACgkQlBXRlnbh1bn0VgCeJB+cBxX1tg1Qgn+MYaW6hS8O
ZX8An3niWwN4lFIbwuBZJ8mKgTBThm6o
=d4lp
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: benchmarking the query planner
Next
From: "Vladimir Sitnikov"
Date:
Subject: Re: benchmarking the query planner