From: | Kate F <kate(at)cats(dot)meow(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Function proposal to find the type of a datum |
Date: | 2007-02-02 16:32:44 |
Message-ID: | 20070202163244.GF390@cats.meow.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb/ 2/07 11:17:46AM -0500, Tom Lane wrote:
> Kate F <kate(at)cats(dot)meow(dot)at> writes:
> > (And whatever the decision regarding ANYELEMENT of, I believe this
> > should behave the same as IS OF)
>
> In the light of morning I think it may be a non-problem. The way that a
> plpgsql function with an ANYELEMENT parameter really works is that on
> first invocation with a parameter of a specific type, we generate a new
> parse-tree on the fly with the parameter being taken as of that type.
> So the IS OF or equivalent operation would never see ANYELEMENT, and
> there's nothing to "look through". (You might check this by seeing if
> IS OF behaves sanely, before you go and spend time on a type_of function
> ...)
I have checked this - I mentioned earlier, when I spoke about my
discussion on IRC with Pavel, but had since forgotten! IS OF for an
array of TEXT yields TEXT. I think this is convenient behaviour
(likewise for the function I'm proposing).
So, to conclude, we still have a valid use-case (which you explained a
little more explicitly than I did). Shall I attempt to implement it?
(that is, type_name_of() which returns TEXT)
Regards,
--
Kate
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-02-02 16:33:31 | proposal: only superuser can change customized_options |
Previous Message | Tom Lane | 2007-02-02 16:17:46 | Re: Function proposal to find the type of a datum |