On Sunday, November 17, 2002, at 10:15 PM, Tom Lane wrote:
> Both of these seem pretty bogus to me. Ideally the driver should not
> issue a "begin" until the application issues the first command of the
> new transaction. Otherwise you get into scenarios where idle
> connections are holding open transactions, and ain't nobody gonna be
> happy with that.
Okay. I think I'll use a flag in the driver to track when it's in a
transaction, and do the right thing in the begin and rollback functions.
> Probably not --- the SQL spec seems to think that the server can intuit
> appropriate datatypes for each parameter symbol. (Which I suppose may
> be true, in a datatype universe as impoverished as the spec's is;
> but it won't work for Postgres. Thus we have a nonstandard syntax for
> PREPARE.) So you'll probably have to do some driver-specific coding
> here.
So, if I understand you correctly, PostgreSQL's PREPARE statement
*requires* data typing in its syntax? If so, is there an
easy/straight-forward way to ask the server what the data types for
each column are before executing the PREPARE?
> No ideas about your other questions, but I hope the DBI folk can
> answer.
Thanks, yes, I'm getting some good responses.
> Go to it ;-)
Thanks Tom!
Regards,
David
--
David Wheeler AIM: dwTheory
david@wheeler.net ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e Jabber:
Theory@jabber.org