From: | David Wheeler <david(at)wheeler(dot)net> |
---|---|
To: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
Cc: | Rudy Lippan <rlippan(at)remotelinux(dot)com>, dbi-dev(at)perl(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: DBD::PgSQL: More Queestions |
Date: | 2002-11-22 01:09:53 |
Message-ID: | 1B6A56C1-FDB7-11D6-8943-0003931A964A@wheeler.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Thursday, November 21, 2002, at 01:44 AM, Tim Bunce wrote:
> MD5 is pretty quick and the base64 result string is short.
Yeah, although then I'd have to hunt up and learn that C API, and then
make sure that it's available on all platforms.
> But if prepared_statement_name's are local to the session then
> you could just use a sequential integer. When a statement handle
> is destroyed then you can tell the server to discard the statement.
Ah, yes, *much* better idea -- thanks!
> You could also let the application specify a name:
>
> $dbh->prepare("...", { pg_sth_name => "..." });
Sounds like a good feature to add later.
Thanks Tim.
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 | David Wheeler | 2002-11-22 01:23:50 | Re: DBD::PgSQL: More Queestions |
Previous Message | David Wheeler | 2002-11-22 01:08:31 | Re: :PgSQL: More Queestions |