> From: Jeff Zucker <[EMAIL PROTECTED]>
> Sent: Saturday, 18 September 2004 12:29 AM
> Subject: Re: :ADO, fetchall_hashref - ok with DBI::PurePerl
> but not DBI :-(

> Hampson, Paul wrote:
> >>From: Jeff Zucker <[EMAIL PROTECTED]>

> >> [DBD::ADO with DBI::Pureperl doesn't exhibit the same bugs
> as with DBI]

> > Ah, this fixed _both_ problems. ^_^

> > The output's the same, too. So I'm well satisfied. And I don't obvserve
> > any speed difference, but that'd be because I'm running against an SQL
> > Server on the other side of the city.

> I'm glad this worked for you, but my intention in mentioning it wasn't
> that users of DBD::ADO should switch to using DBI::Pureperl, rather that
> the information on the difference might be useful in tracking down the
> bug.   I hope that you see DBI::PurePerl as a temporary solution until
> the problem is resolved.

Well, I think it did help in narrowing down the problem, as I
said in my email on the other side of the thread. However, as
I want to deploy this _now_, I've deployed with DBI::PurePerl,
with a comment regarding the issue and versions involved that
myself or whoever else plays with it will see.

--
Paul Hampson

A: Because it's hard to read.
Q: Why is top-posting discouraged?

************************************************************************
*PLEASE NOTE*  This email and any attachments may
be confidential. If received in error, please delete all
copies and advise the sender. The reproduction or
dissemination of this email or its attachments is
prohibited without the consent of the sender.

WARNING RE VIRUSES:  Our computer systems sweep
outgoing email to guard against viruses, but no warranty
is given that this email or its attachments are virus free.
Before opening or using attachments, please check for
viruses.  Our liability is limited to the re-supply of any
affected attachments.

Any views expressed in this message are those of the
individual sender, except where the sender expressly,
and with authority, states them to be the views of the
organisation.
************************************************************************

Reply via email to