On Fri, Jun 01, 2001 at 10:25:51AM +0100, Graham Barr wrote:
> On Fri, Jun 01, 2001 at 10:23:39AM +0100, Graham Barr wrote:
> > On Fri, Jun 01, 2001 at 10:19:51AM +0100, Tim Bunce wrote:
> > > Thanks. I'll fix it for the next release. Meanwhile try
> > >
> > > ... $attr ? sort %$attr : ();
> >
On Fri, Jun 01, 2001 at 10:23:39AM +0100, Graham Barr wrote:
> On Fri, Jun 01, 2001 at 10:19:51AM +0100, Tim Bunce wrote:
> > Thanks. I'll fix it for the next release. Meanwhile try
> >
> > ... $attr ? sort %$attr : ();
>
> Um, that will mix the kesy and values. You would need something like
On Fri, Jun 01, 2001 at 10:19:51AM +0100, Tim Bunce wrote:
> Thanks. I'll fix it for the next release. Meanwhile try
>
> ... $attr ? sort %$attr : ();
Um, that will mix the kesy and values. You would need something like
... $attr ? map { ($_,$attr->{$_}) } sort keys %$attr : ()
Graham.
Thanks. I'll fix it for the next release. Meanwhile try
... $attr ? sort %$attr : ();
Tim.
On Thu, May 31, 2001 at 04:17:09PM -0500, Mitch Helle-Morrissey wrote:
> I think there might be a bug with the connect_cached() method in DBI. If
> the elements in the attributes hashref are in a
I think there might be a bug with the connect_cached() method in DBI. If
the elements in the attributes hashref are in a different order, then it
makes a new handle instead of returning the cached handle, even if they are
the same values. This presents a problem if you are generating the
attribu
