On Thursday, August 22, 2002, at 07:17 AM, David Wheeler wrote:
> + # XXX add $attr{HandleError} logic here? Yes!
> +$attr->{HandleError}($msg, $drh, $dbh)
> + if UNIVERSAL::isa($attr->{HandleError}, 'CODE');
>
D'oh! Did it again! Here it is with the arrow opera
On Thursday, August 22, 2002, at 06:17 AM, Ronald J Kimball wrote:
> That syntax is not supported in perl5.005; the arrow before the
> subroutine
> arguments was required until perl5.6.
Ah, yes, I actually was wondering about that.
> It might also be good to make sure $attr->{HandleError} is
On Wed, Aug 21, 2002 at 09:59:23PM -0700, David Wheeler wrote:
> Hi All,
>
> I'd like to submit a simple patch that causes the DBI connect() method
> to execute a HandleError code reference if it has one. There's a
> comment suggesting that it could be added, and it makes sense to me, so
> I s
Hi All,
I'd like to submit a simple patch that causes the DBI connect() method
to execute a HandleError code reference if it has one. There's a
comment suggesting that it could be added, and it makes sense to me, so
I submit this patch.
--- DBI.pm.org Wed Aug 21 21:09:27 2002
+++ DBI.pm
I agree that your "insane" example is unjustifiable, and I wouldn't complain if you
choose to disregard it. I don't think I would ever use "odbc_force_rebind".
> Now -- a question for you: would you *like* to know how many rows were
> affected by the inserts/updates inside your stored procs or
Hi, I'm back from vacation. I see you and Martin have been discussing my latest
reported bug at length. I don't understand the full discussion, but I think I get the
gist of the problem, i.e., that there's a fundamental probem in DBD::ODBC when a
stored procedure performs heterogeneous SELECT
