This message follows after my last "commoditization suggestion #1" email.
For a context, I reference this portion of the DBI user
documentation, under disconnect():
The transaction behaviour of the disconnect method is, sadly,
undefined. Some database systems (such as Oracle and Ingres) will
a
Someone has logged a bug against DBD::Informix because it wasn't
cleaning up properly as a handle was destroyed. It turns out that the
statement-level active flag was not set. But, simply setting it on
means DBD::Informix runs foul of all sorts of issues during destroy.
Of course it's a bug t
Thanks much. I'll be returning from travel early next week and will look into this
then.
--
Jeff
> -Original Message-
> From: Jan Dubois [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 12, 2004 02:01 AM
> To: [EMAIL PROTECTED]
> Cc: ''Tim Bunce'', [EMAIL PROTECTED]
> Subject: Re: DB
Merijn wrote:
>
>HP-UX 11i (11.11) + perl-5.8.5-dor + DBI-1.43 + DBD-CSV-0.21
>
>Failed Test Stat Wstat Total Fail Failed List of Failed
>---
>t/40bindparam.t 281 3.57% 14
>Failed 1/14 test script
Some of my mail seems to be getting lost. Just seeing if this
message gets through the list. Don't reply to it. -- sayeth I
> Comments welcome.
Just some random thoughts that came from reading this.
What about Multiple result set statements/more_results? (i.e. select * from
foo; select * from bar; or calling stored procs which have multiple
statements within them as per Sybase & SQL*Server, etc)
[snip]
>
> =head2
At 5:42 PM +0200 8/10/04, H.Merijn Brand wrote:
Unsure if this is the right spot, but in writing the DBD I found the
unidirection from handle to handle quite restrictive.
Statement handles know what database handle they belong to, but database
handles don't know what statement handles are opened on
At 5:42 PM +0200 8/10/04, H.Merijn Brand wrote:
Unsure if this is the right spot, but in writing the DBD I found the
unidirection from handle to handle quite restrictive.
Statement handles know what database handle they belong to, but database
handles don't know what statement handles are opened on
