| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
| Subject: | Re: Use UNKNOWN with PL/Perl spi_prepare()? |
| Date: | 2010-04-07 00:27:48 |
| Message-ID: | 1E4F4D5B-337A-48D8-BD9E-A2F0225E45C3@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 6, 2010, at 5:06 PM, Tom Lane wrote:
> Somehow, emulating the above doesn't attract me nearly as much as it
> evidently does you. What happens in cases where the parser is unable
> to infer a data type, or infers the wrong one?
An exception should be thrown.
> Or even if it does
> infer a type, how do you find out what it inferred?
Since I'm fetching the data from PL/Perl, I don't really care.
> I'm not excited
> about building a capability that fails to address any except the simplest
> use case.
It will save me a ton of duplicate code.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-04-07 00:28:28 | Re: Use UNKNOWN with PL/Perl spi_prepare()? |
| Previous Message | Andrew Dunstan | 2010-04-07 00:23:57 | Re: Use UNKNOWN with PL/Perl spi_prepare()? |