From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
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:06:57 |
Message-ID: | 1298.1270598817@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> DBD::Pg makes extensive use of unknown for prepares. If I do
> my $sth = $dbh->prepare('SELECT foo FROM bar WHERE baz = ?');
> DBD::Pg effectively sends:
> PREPARE dbdpg_1(unknown) AS SELECT from FROM bar WHERE baz = ?';
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? Or even if it does
infer a type, how do you find out what it inferred? I'm not excited
about building a capability that fails to address any except the simplest
use case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-04-07 00:23:57 | Re: Use UNKNOWN with PL/Perl spi_prepare()? |
Previous Message | David E. Wheeler | 2010-04-07 00:02:25 | Re: Use UNKNOWN with PL/Perl spi_prepare()? |