From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |
Date: | 2012-05-03 15:12:14 |
Message-ID: | 23934.1336057934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2012/5/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> No, it isn't, at least not if you have any ambition to support array
>> types for instance; to say nothing of types whose standard names are
>> keywords, multiple words, etc.
> we can identify a position "anytypename" before raising error - it can
> be similar to current identification of PL/pgSQL variables inside
> expression. Probably it is too complex for this issue :(
[ shrug ... ] Feel free to spend time that way if you want to, but
I'm entirely confident that you won't come out with anything except
an ugly, unmaintainable, incomplete kluge.
> Maybe some keyword can help to us. What do you think about new
> operator TYPE that can returns regtype value and can be used together
> with polymorphic functions.
Doesn't have any more attraction for me than the proposed LIKE
extension; that will have the same results and it's at least traceable
to SQL-standard notations.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-05-03 15:20:32 | Re: "unexpected EOF" messages |
Previous Message | Tom Lane | 2012-05-03 15:06:53 | Re: "unexpected EOF" messages |