On Wed, Feb 15, 2006 at 11:02:55AM +0000, Dave Howorth wrote:
> [EMAIL PROTECTED] wrote:
> >IMO (and I may be off base), it should be possible to use Loader, which
> >will have a standard set of predictable results (which should be
> >detailed in the docs), and then only write your own classes for the
> >parts you need to change / expand. Some flag should possibly set whether
> >the user-created classes replace or extend the Loader ones .. ?
>
> FWIW, that's what I do in my home-grown CDBI/Maypole loader. It works
> well for me. I haven't needed to replace any automatically-generated
> classes; I just override individual methods. For example, I define an
> alternate semantics for find_or_create in my base class and override the
> method in those classes where it's appropriate (some classes have
> special change-logging built in that alters how the find part of
> find_or_create needs to work).
>
> It would be nice when I get around to migrating to find that DBIC
> already has the mechanism :)
left_base_classes and additional_base_classes should already do the trick
for this in all Loaders (including the CDBI one)
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/