On Fri, Dec 10, 2010 at 2:44 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 2010/12/10 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>>> 2010/12/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>>> What exactly is the use-case for that?
>>> I am working on function that can help with record updating. It's
>>> based on polymorphic types. I would to allow a multiple modification
>>> per one call - like UPDATE statement does.
>>> some like:
>>> record_set_fields(anyelement, key text, value "any" [, key text, value
>>> "any" [..]]) returns anyelement
>> OK, makes sense, since you don't want to constrain the values to be all
>> the same datatype.
> ok, can I send a patch?
In the part of Tom's email you didn't quote, he wrote "this can't
work". Did you miss that part?
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Andrey G.||Date: 2010-12-13 21:28:55|
|Subject: Re: BUG #5776: Unable to create view with parameter in PL/pgsql|
|Previous:||From: tushar||Date: 2010-12-13 08:45:35|
|Subject: Re: BUG #5789: asking password|