Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"

[prev] [thread] [next] [Date index for 2005/07/26]

From: Matt S Trout
Subject: Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"
Date: 23:02 on 26 Jul 2005
On Tue, Jul 26, 2005 at 03:21:26PM -0700, Michael G Schwern wrote:
> On Tue, Jul 26, 2005 at 06:05:02PM -0400, Perrin Harkins wrote:
> > I suspect Sebastian just meant that delegation requires you to decide
> > ahead of time what sort of things can be changed in your class, e.g. SQL
> > generation, accessor generation, etc.  You have to setup a specific list
> > of things that are  delegated and thus can be changed.
> 
> And dividing things up into multiple classes you inherit from doesn't?

Not to nearly the same extent. Let me run an example past you (which you've
asked for in a couple of mails now but I have to pick one to reply to :)

Say you have a DBIC add-on called DBIC::Foo that adds an extra feature,
and another caleed DBIC::Bar that does the same thing. Both use nice, simple
delegation to override their foo_handler and bar_handler code, but obviously
can't be installed themselves with delegates because they add extra stuff
that isn't a part of the current delegation API.

How do I use them both in the same system apart from with

use base qw/DBIC DBIC::Foo DBIC::Bar/;

?

        -- 
             Matt S Trout           Website: http://www.shadowcatsystems.co.uk
  Technical Director        E-mail:  mst (at) shadowcatsystems.co.uk
Shadowcat Systems Ltd.

(message missing)

Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"
Matt S Trout 23:02 on 26 Jul 2005

Delegation vs Hooks (was: Annouce: DBIx::Class, a.k.a "taking the easy way out")
=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= 23:27 on 26 Jul 2005

Generated at 16:37 on 28 Jul 2005 by mariachi v0.52