Ah, cool, I'd call that 'break handling'.

[It's been on my DBI to-do for years as "Add 'break handling' when
field values change? Use two fbav's so 'previous record' is available.
Define break fields and handlers. Call them via an alternate
fetch_with_break method."]

'Loop' is a bit vague. How about...

DBIx::
::FetchLoop       bdpOg Fetch with change detection and aggregates   BITS

Tim.


On Wed, Jan 02, 2002 at 12:02:16AM -0500, Brendan Fagan wrote:
> 
> http://www.xray.mpe.mpg.de/mailing-lists/modules/2001-12/msg00405.html
> 
> As I stated earlier, I could stand to elaborate more in the docs, but the
> module is relatively straightforward (even if my one line description
> needs work).
> 
> Hope this will suffice.
> 
> - Brendan
> 
> On Tue, 1 Jan 2002, Tim Bunce wrote:
> 
> > On Tue, Jan 01, 2002 at 11:17:18AM -0500, Brendan Fagan wrote:
> > > 
> > > Tim, 
> > > 
> > > Thanks for resending the message, but I'm not clear as to why.   I did
> > > already send the docs.  
> > 
> > I haven't seen them. Please repost them or a url.
> > 
> > > How about "Supplemental DBI methods for looping, aggregation and
> > > concatenation of data"?
> > 
> > Too long :)
> > 
> > > Happy new year!
> > 
> > Thanks! And you.
> > 
> > Tim.
> > 
> > > - Brendan
> > > 
> > > On Sat, 29 Dec 2001, Tim Bunce wrote:
> > > 
> > > > On Sat, Dec 29, 2001 at 05:13:32PM +0100, Perl Authors Upload Server wrote:
> > > > > 
> > > > > The following module was proposed for inclusion in the Module List:
> > > > > 
> > > > >   modid:       DBIx::Loop
> > > > >   DSLIP:       bdpOg
> > > > > 
> > > > >     In following the other DBI extension modules, I choose the DBIx
> > > > >     rootlevel namespace. Loop is fairly straightforward as it is a
> > > > >     utility module for simplified looping logic.
> > > > > 
> > > > > DBIx::
> > > > > ::Loop            bdpOg Simple Looping routines for DBI              BITS
> > > > 
> > > > Umm, "Simple Looping routines for DBI" doesn't really explain very much.
> > > > Perhaps you could reply with the docs.
> > > > 
> > > > Tim.
> > > > 
> > > 
> > 
> 

Reply via email to