Hello Laurent, On Mon, Jun 07, 2010 at 08:56:04AM +0200, Dami Laurent (PJ) wrote: > Salut Marc, > > Various ORMs differ in modelling schema and tables : some use classes, > some use object instances. Old Class::DBI was class-based. DBIx::Class > was initially class-based, and then switched to instance-based after a > couple of months of existence.
My way to instance-based is quiet similar: I discovered ORMs with activerecord and was very happy ... 'til the day i had to compare 2 databases :) I seen DBIx::Class is much more flexible but i franckly miss the activerecord's ease of use and i don't need extended features in a large majority of cases. That's why i'm trying to add simplicity over DBIx::Class, using it when it's possible. > Since DBIx::Class explicitly chose the instance-based approach, you > have to stick to it, or change ORM, but don't add class-based access > on top of an instance-based framework, or you will end up in a > conceptual mess. Yeah ... it's hard to choose an ORM without having experience and knowledge about different stragegies. One of the things i really would have to keep choosing another ORM is the resultset_class to make the ORM able to produce Moose objects on fly but reading your post again, i realize my problem is i can't figure out how to build a set of business classes on top of a insance-based ORM with DRY compliance. I have to test and read again ... perhaps by reading some existent code using DBIx::Class. What are the DBIx::Class based major applications ? Regards Marc _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
