Tim Bunce wrote:
> My current plan is to add a $h->{HandleEvent} = sub { ... }
> hook that can be used for SUCCESS_WITH_INFO and other events the
> driver may want to communicate back to an application.
>
> Meanwhile I suggest that you add a $h->{ado_event} = sub { ... }
> and and use that however you think best. Your experience can feed
> back into the HandleEvent design.
O.k., but set_err() - how about that (for now)?
Should it be called or not? Or should it be called with
err == 0, which makes errstr and state accessible (if not
overwritten with the next error), but doesn't trigger the
normal DBI error handling mechanisms?
Steffen
