On Fri, Jul 05, 2002 at 05:55:09PM -0700, David L. Good wrote: > I'm afraid I've come into this in the middle of things. I only subscribed > to dbi-dev when you suggested discussing this there (I either forgot or > didn't know there was a dbi-dev or I would have come here earlier -- I didn't > expect I'd be hacking on DBD::ODBC again anytime soon). I've looked through > the archives a bit, but I'm afraid I don't quite know what is the purpose of > HandleEvent.
It has two primary goals: 1/ provide a way to deal with the 'success with info' concept. 2/ provide a way to deal with messages from the database. and of course the API would be designed to be extensible and drivers will be free to use it for other things. > In DBD::Sybase the syb_err_handler sub gets called > with 7 parameters. In my patch to DBD::ODBC, there's only two: SQLSTATE > (probably only of interest to hard-core ODBC programmers) and the error > message. Okay. > As far as return value goes, I think Michael Peppler had the right idea > when he decided to have the return value be a simple true/false value that > just determines whether you want the "error" to be processed normally (via > RaiseError or PrintError) or not. Yes, that's probably what I'd do. Tim.
