Re: Time to Document Callbacks

On Fri, Oct 30, 2009 at 01:42:03PM +0100, H.Merijn Brand wrote:
> On Fri, 30 Oct 2009 12:31:03 +0000, Tim Bunce <[email protected]>
> wrote:
> 
> > On Thu, Oct 29, 2009 at 05:10:07PM -0700, David E. Wheeler wrote:
> > > On Oct 29, 2009, at 4:24 PM, Tim Bunce wrote:
> > >
> > >> I could arrange for Callbacks to only apply to methods called by the
> > >> applicationi, and not to 'nested calls'. That's a fairly major change
> > >> after this length of time but given the limited use Callbacks have had,
> > >> and the lack of documentation, it's not out of the question.
> > >>
> > >> The downside is that to intercept all fetched rows in a general way
> > >> (like some kind of plugin utility module might want to do) you now have
> > >> to add callbacks for 7 $sth fetch* methods and 6 $dbh select* methods.
> > >>
> > >> Is that really preferable?
> > >
> > > Well, yes.
> > 
> > Okay. Anyone else care to express an opinion?
> 
> So far I didn't really follow. I just assumed that all would go well.
> Will any of this influence DBD authors to have to change/add/update
> their modules?

No. Callbacks are handled entirely by the DBI method dispatcher (like
RaiseError, for example).

Tim.