Thanks for the quick reply,
I will probably not have the time to make the changes in the next couple of
weeks. But as I am in the position of wanting Perl on NT to talk to multiple
data sources and would prefer to use ADO, I will try and make the changes to
ado.pm and send it to you. When I can.
Not sure about your answer to 1. If I pass thru a connect string with
....;IsolationLevel=adXactBrowse;.... Then in the STORE function you could
access check $value to see if existed in $ado_consts. Or I think that I am
actually exposing my lack of understanding about what $this->STORE is
actually doing.
Tim
-----Original Message-----
From: Thomas A. Lowery [mailto:[EMAIL PROTECTED]]
Sent: 06 June 2001 19:22
To: [EMAIL PROTECTED]
Subject: Re: Question regarding dbi:ADO isolation level,Connection and
command properties , and streams
Importance: Low
On Wed, Jun 06, 2001 at 11:17:25AM +0100, [EMAIL PROTECTED]
wrote:
> Hi all I have a few questions that I have not seen anything in the
archives
> for. I have ADO2.1 installed on DBI 1.16
> 1. dbi:ADO supports setting Isolation Level but only as a number. Is there
a
> reason that it does not seem to use the ado_const's, eg adXactBrowse
I haven't exported these constants from the module for the calling
application. I'll add it to the To-Do list.
> 2.dbi:ADO supports setting Connectiontimeout and CommandTimeout in the
> connection string but I have discovered that ADO does not let a command
> inherit its connections Command and Connection timeout values
> see the following (also quoted below)
> http://msdn.microsoft.com/library/psdk/dasdk/mdap4wc4.htm
>
> "The CommandTimeout setting on a Connection object has no effect on the
> CommandTimeout setting on a Command object on the same Connection; that
is,
> the Command object's CommandTimeout property does not inherit the value of
> the Connection object's CommandTimeout value." </quote>
>
> the upshot of which was a long query (over 9 minutes) was failing with a
> timeout.
I thought I had support for inheriting the CommandTimeout from the
Connection object, but reviewing the code, it doesn't.
> I have made a addition to my copy of ado.pm to add this to the %attr that
> you can pass through on a prepare, and it seems to work.
Great! Send me a patch (prefer diff -c) and if possible, a "test(s)" for
the change.
> 3. Is there a reason that Stream support should not be added to ADO.pm.
Has
> anyone experimented with this
The short answer: No. Not I. Please feel free and encouraged to do so.
The long answer:
When I did most of my development on DBD::ADO, I worked in an Windows NT
environment with HP large database servers. All the desktops, web
servers, and some database servers where Windows based. ADO was prefect
for integrating the numerous data sources.
Since August 2000, I changed positions to a Linux and Sun based
environment with very little interaction with Windows. Occasionally I
still need a Windows data source, but not day to day.
Additionally, I've an older version of VC++ (5.0 sp3), which I finding
doesn't work with the newer version of Activestate Perl (for building
modules either not supplied by PPM or installing more current versions).
I haven't shelled out the money for a newer compiler, yet.
What this means is development time (for me) on DBD::ADO is very limited
now. If you've features or changes, please send me patches, documents,
and/or tests.
Thomas
--
Thomas A. Lowery
See DBI/FAQ http://tlowery.hypermart.net
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.
------------------------------------------------------------------------
