Re: actualised funcs typmod patch - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: actualised funcs typmod patch
Date
Msg-id 162867790911171220h2908ecd0hc0424fce6c1e6de5@mail.gmail.com
Whole thread Raw
In response to Re: actualised funcs typmod patch  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
2009/11/17 Kevin Grittner <Kevin.Grittner@wicourts.gov>:
> Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
>> sorry, it's problem in my english
>
> In hopes that it may help overcome the language barrier if someone
> restates the issue in different words, I'll echo Tom's concerns, which
> I share.
>
>> This cannot change an behave of older applications.
>
> Agreed.  That's not the problem.
>
>> if somebody use explicit typmod in CREATE FUNCTION statement, then
>> he get different behave. But he have to do it explicitly in 8.5.
>
> The problem here is that we are then committed to supporting that
> behavior forever.  There are many different options for what behavior
> could and should be supported for this syntax, and we don't want to
> get locked in to one of those options by happenstance.  We want the
> options to be discussed by the community prior to getting locked in to
> something.  It would be unusual for one individual to pick a direction
> for something like this and to come up with a decision which is as
> good, in the long run, as consensus coming out of the synergy of group
> discussion could generate.

I understand it well and I invite any discussion about this topic
(additing typmod to function's interface). So please, check it, test
it, write notes.

Pavel

>
> -Kevin
>


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: actualised funcs typmod patch
Next
From: Robert Haas
Date:
Subject: Re: plpgsql: open for execute - add USING clause