RE: :ODBC: connect() attributes

On 27-Feb-2002 Jeff Urlwin wrote: Steffen, Thanks! Are you not getting ODBC 3.x behavior by default? I doubt it as dbdimp.c calls SQLAllocEnv, SQLAllocConnect - ODBC 2.0 calls which suggest to the driver you want ODBC 2.0 behavior. To get ODBC 3.0 behavior you need to ask for it with

Re: DBD::ODBC: connect() attributes

Jeff Urlwin wrote: Are you not getting ODBC 3.x behavior by default? Yes, at least for the Oracle ODBC driver. In the past I used MS ODBC Test to capture test data like http:[EMAIL PROTECTED]/msg00359.html where I could set SQL_ATTR_ODBC_VERSION. Now it's possible to do it with DBD::ODBC

RE: DBD::ODBC: connect() attributes

I'm patching that into DBD::ODBC 0.39. I might release it soon-ish, but I want to find out why ActiveState has not put 0.38 in their repository first. Regards, Jeff -Original Message- From: Steffen Goeldner [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 5:27 AM To:

where should database pinging be automatic within the DBI(x::AnyDBD)? API?

Call me paranoid I have never ever had a database connection die after I got it However, I feel funny writing a book on coding Industry-Strength DBI (co-authors welcome) without being able to say and via this attribute or hook, all of your calls to your database application handle will

Re: where should database pinging be automatic within the DBI(x::AnyDBD)?API?

On Wed, 31 Dec 1969, Terrence Brannon wrote: Call me paranoid I have never ever had a database connection die after I got it However, I feel funny writing a book on coding Industry-Strength DBI (co-authors welcome) without being able to say and via this attribute or hook, all of your