| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Raphaël Jacquot <sxpert(at)sxpert(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: wishlist for 8.4 |
| Date: | 2008-02-15 01:12:47 |
| Message-ID: | 9CAB5085-B22E-48C4-B7B4-11EC33CAC9FE@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 14, 2008, at 10:06 AM, Tom Lane wrote:
> =?UTF-8?B?UmFwaGHDq2wgSmFjcXVvdA==?= <sxpert(at)sxpert(dot)org> writes:
>> so, I propose the use of
>> NEW[variable_containing_the_column_name]
>> (which can obviously be extended to any tuples)
>> to allow such access.
>
>> what do you experts think ?
>
> Zero chance. plplgsql is a strongly typed language, and a construct
> like that couldn't have any known-in-advance data type.
Would it be reasonable to teach EXECUTE about NEW and OLD? That
should allow the OP to do what he's looking for...
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Decibel! | 2008-02-15 01:19:02 | Key for grant attributes (was: Re: Show INHERIT in \du) |
| Previous Message | Brendan Jurd | 2008-02-15 00:09:44 | Re: Show INHERIT in \du |