On Mon, Aug 18, 2008 at 09:40:52PM -, Greg Sabino Mullane wrote:
>
> > The finish() docs say:
> >
> > Calling C resets the L attribute for the statement. It
> > may also make some statement handle attributes (such as C and
> > C)
> > unavailable if they have not already been accessed (and
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> The finish() docs say:
>
> Calling C resets the L attribute for the statement. It
> may also make some statement handle attributes (such as C and C)
> unavailable if they have not already been accessed (and thus cached).
Sure, but why is
The finish() docs say:
Calling C resets the L attribute for the statement. It
may also make some statement handle attributes (such as C and C)
unavailable if they have not already been accessed (and thus cached).
Tim.
On Thu, Aug 07, 2008 at 04:29:25PM -, Greg Sabino Mullane wrote:
>
On Aug 7, 2008, at 09:29, Greg Sabino Mullane wrote:
For DBD::Pg, it prints:
$VAR1 = [
'Goldfish'
];
$VAR1 = [
'goldfish'
];
$VAR1 = undef;
$VAR1 = [
'goldfish'
];
$VAR1 = undef;
DBD::SQLite:
$VAR1 = [
'Goldfish'
];
$VAR1 = [
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I noticed something odd with NAME and NAME_lc / NAME_uc: if
they are called, and then called *again* after $sth->finish()
is called, both NAME_lc and NAME_uc return the previous values
instead of an undef. I'm not sure if this is a DBI or
DBD::P
