From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 14:42:07 |
Message-ID: | CAFj8pRDtopH2ws1L7cXEPmEezsfivkmK_z2EQg8hn8C9TtstFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2012/5/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> You guys seem to be taking the original proposal off into the weeds. I
>> have often wanted to be able to use LIKE in type expressions, and I'd
>> like to see exactly that implemented.
>
> This notion of "anytypename" is utterly unworkable anyway; there's no
> way for the parser to know soon enough that a given argument position
> needs to be read as a type name rather than a normal expression.
> You could conceivably make it work with the argument being a regtype
> literal (ie, quoted); but that seems at least as klugy as what hstore
> is doing.
>
type identifier is same identifier like other - but I have no
prototype now, so I don't know if there is some trap
I remember so I though about using CAST keyword too
some like SELECT CAST( populate_record(hstore_value) AS type)
Regards
Pavel
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-05-03 14:44:57 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |
Previous Message | Tom Lane | 2012-05-03 14:33:12 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |