From: | David Wheeler <david(at)wheeler(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | dbi-dev(at)perl(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: DBD::PostgreSQL |
Date: | 2002-11-18 16:27:33 |
Message-ID: | A3F94BB8-FB12-11D6-93B3-0003931A964A@wheeler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
On Monday, November 18, 2002, at 08:19 AM, Tom Lane wrote:
> I think someone else said that the DBD framework already includes such
> a
> flag ("BegunWork"?) --- if so, you should surely use that one.
No, I'm finding out that that flag is for a slightly different purpose
-- using transactions even when AutoCommit = 1.
>> So, if I understand you correctly, PostgreSQL's PREPARE statement
>> *requires* data typing in its syntax?
>
> Yup.
Damn.
> There are various ways to retrieve the datatypes of the columns of a
> table, but I'm not sure how that helps you to determine the parameter
> types for an arbitrary SQL command to be prepared. Are you assuming
> a specific structure of the command you want to prepare?
Ouch, good point. I don't want to go there. It's a shame, really, but
in light of this requirement, I don't see how PostgreSQL prepared
statements can be supported by the DBI. Pity; I was really looking
forward to the performance boost.
Regards,
David
--
David Wheeler AIM: dwTheory
david(at)wheeler(dot)net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: Theory(at)jabber(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SB SD | 2002-11-18 16:32:25 | Re: [GENERAL] DECLARE CURSOR |
Previous Message | Tom Lane | 2002-11-18 16:19:25 | Re: DBD::PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Bunce | 2002-11-18 16:39:08 | Re: DBD::PostgreSQL |
Previous Message | Tom Lane | 2002-11-18 16:19:25 | Re: DBD::PostgreSQL |