On Mon, 3 Dec 2001 17:20:24 +0000, Tim Bunce wrote:
> On Sat, Dec 01, 2001 at 01:19:47PM -0500, Thomas A.Lowery wrote:
> > This is a good idea. I'm wondering what other "Defaults" to allow for?
>
> The attribute should be named 'ado_...', the underscore is part of
> the driver-private name prefix.
This is one reason why I said it should not be taken as-is :-)
Another reason is my 'hack' feels like one. It just does not
feel like production code for some reason...
before inclusion I welcome more experienced DBD developers to
provide thier feedback... Being as tired as I was I am pretty
sure I did something else wrong :-(
> Beware of the performance cost of all these extra little attributes.
> It's a cost paid by all even if not used.
Yes - however I *need* this one (somehow) as the alternative is some
major hacking of a *lot* of source code to work around the tatty
SqlServer ADO driver only - I hope :-)
If it was rejected (and I was waiting for it!) I would have included an
ENV lookup or similar and would have had to support the 'hack' myself.
Not my preferred solution but if neede to get the job done... :-(
> Tim.
>
> > Any which should be inherent to child handles?
> >
> > Tom
> >
> > On Fri, Nov 30, 2001 at 02:11:56PM +0000, Jacqui Caren wrote:
> > > Rather than code prepare and do attrs across the entire
> > > application I 'hacked' a $dbh attribute named
> > > 'adoDefaultCursorType'
> > >
> > > This allows me to do
> > >
> > > $dbh->{adoDefaultCursorType} = 'adOpenStatic';
> > >
> > > and I then automatically use Open Static cursors
> > > everywhere. Life is good and I get to go home and
> > > eat a hot meal :-)
p.s. I meant the hot meal bit - this project has been a bit
of a nightmare and I need to deliver a working and tested
system this week. MS ODBC for db replication via perl is a joke
and the DBD::ADO driver is the only alternative as I have
to sync both DB's and file based repositories in the right
order.
<WHINE>
The code I now have is working but we still have to include
the many other workarounds for problems such as
Sqlserver adding 'blocked' nulls to end the of TEXT/IMAGE fields
etc. IMHO how anyone could call the SQLserver ADO driver (I'm not
talking about DBD::ADO* here) commercial quality code is beyond
understanding. The bugs we see are so basic I wonder what MS
developers are paid to do all day...
</WHINE>
Once delivered I get some hols - so please be gentle :-)
Jacqui Caren, Ingram Group Ltd. [EMAIL PROTECTED]
ph: +44 (0) 1483 8628xx main=00 fax=01 ddi=65
http://www.ig.co.uk/ http://www.sitedirector.org/
http://www.perl.co.uk/
