On Tue, Aug 10, 2004 at 10:38:31AM -0700, Henri Asseily wrote:
>
> >* The DBD::Multiplex driver is intended to enable a wide range of
> >dynamic functionality including support for various high-availability
> >and load-balancing scenarios. The old version has been used
> >successfully but was lim
On Tue, Aug 10, 2004 at 10:44:49PM -0700, Jonathan Leffler wrote:
>
> DBD::Informix has always implemented things so that the $drh has a
> list of the $dbh that have been opened on it, and each $dbh has a list
> of the $sth that have been created on it. But I don't particularly
> like having t
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
> 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
Michael Peppler wrote:
On Tue, 2004-08-10 at 17:42, H.Merijn Brand wrote:
On Tue 10 Aug 2004 00:52, Tim Bunce <[EMAIL PROTECTED]> wrote:
Comments welcome.
=head1 DBI ROAD-MAP
9th August 2004
This document aims to provide a high level overview of the future direction of the DBI.
It outlines the broa
On Tue, Aug 10, 2004 at 05:42:05PM +0200, H.Merijn Brand wrote:
> On Tue 10 Aug 2004 00:52, Tim Bunce <[EMAIL PROTECTED]> wrote:
> > Comments welcome.
> >
> >
> > =head1 DBI ROAD-MAP
> >
> > 9th August 2004
> >
> > This document aims to provide a high level overview of the future direction of t
On Tue, Aug 10, 2004 at 04:28:39PM -0400, Jeff Urlwin wrote:
>
> > 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
>
* A DBI handle is a reference to a tied hash and so has an 'outer'
hash that the handle reference points to and an 'inner' hash holding
the DBI data. By allowing the inner handle to be changed, for
example swapped with a different handle, many new behaviors become
possible. For example a database
On Tue, 2004-08-10 at 17:42, H.Merijn Brand wrote:
> On Tue 10 Aug 2004 00:52, Tim Bunce <[EMAIL PROTECTED]> wrote:
> > Comments welcome.
> >
> >
> > =head1 DBI ROAD-MAP
> >
> > 9th August 2004
> >
> > This document aims to provide a high level overview of the future direction of the
> > DBI.
On Tue, 2004-08-10 at 17:42, H.Merijn Brand wrote:
> On Tue 10 Aug 2004 00:52, Tim Bunce <[EMAIL PROTECTED]> wrote:
> > Comments welcome.
> >
> >
> > =head1 DBI ROAD-MAP
> >
> > 9th August 2004
> >
> > This document aims to provide a high level overview of the future direction of the
> > DBI.
On Tue 10 Aug 2004 00:52, Tim Bunce <[EMAIL PROTECTED]> wrote:
> Comments welcome.
>
>
> =head1 DBI ROAD-MAP
>
> 9th August 2004
>
> This document aims to provide a high level overview of the future direction of the
> DBI.
>
> It outlines the broad categories of changes, along with some ratio
At the risk of speaking redundantly, I volunteer myself to co-lead
the common test suite effort, citing the benefits that Tim listed.
Considering that my own wrapper over DBI ("Rosetta") is intended to
have a very rigorously defined API and behaviour from an
application's/user's point of view,
14 matches
Mail list logo
