| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, depesz(at)depesz(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Dyamic updates of NEW with pl/pgsql |
| Date: | 2010-03-15 16:19:13 |
| Message-ID: | 19387.1268669953@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Mon, Mar 15, 2010 at 11:37 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> If we make the implementation be such that "(rec->field)::foo" forces
>> a runtime cast to foo (rather than throwing an error if it's not type
>> foo already)
> yeah...explicit cast should always do 'best effort'
Probably so. But is it worth inventing some other notation that says
"expect this field to be of type foo", with an error rather than runtime
cast if it's not? If we go with treating the result of -> like UNKNOWN,
then you wouldn't need that in cases where the parser guesses the right
type. But there are going to be cases where you need to override the
guess without necessarily wanting to buy into a forced conversion.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-03-15 16:53:45 | Re: Dyamic updates of NEW with pl/pgsql |
| Previous Message | Merlin Moncure | 2010-03-15 16:14:03 | Re: Dyamic updates of NEW with pl/pgsql |