At 4:52 pm +0100 10/9/01, Tony Bowden wrote (to the TT list): >On Mon, Sep 10, 2001 at 03:48:42PM +0100, will wrote: >> I'm passing little bunches of Class::DBI objects through to a >> template. It's working very well, but some of their more rarely-used >> methods involve quite laborious database work, and i'd like to avoid >> invoking those methods unless the template requests them. > >This should just happen OK ...
sheepish. it does now. i was just checking that it was possible before i tried to find out where i'd b0rken it. there's something profoundly satisfying about triggering the database queries from the templates just as they're needed, in a perfectly abstract way and without compromising the pipeline at all. worship the module, indeed. >I use TT with Class::DBI all the time (*grin*), and have had no >problems. In fact Class::DBI + Template::Toolkit is probably one of >the most powerful ways I've encountered of giving designers great >flexibility really quickly. ...so do i, now. i'm shifting everything over just as fast as i can type it. the only thing i've added in subclass is a retrieve_where() based on the one in MasonHQ (but with sort and limit clauses). otherwise it does just exactly what i need it to. thank you. will ps. my slightly silly question received friendly answers from the authors of both modules within an hour or so. that's some support contract.
