do most users of RDBO tend to stick to the Thing and Thing::Manager
pattern from the docs and tutorial?
my $thing = Thing->new(...)->load;
my @things = Thing::Manager->get_things(...);
it seems like a lot of classes to juggle, when i'm looking at 100+
tables in the schema ..
what headaches might one run into if the manager methods are created
on the Thing class instead?
my $thing = Thing->new(...)->load;
my @things = Thing->get_things(...);
alternatively, has anyone implemented a pattern using single manager
class that manages all tables?
my @those = TheOneTrue::Manager->get_those(); # returns Those objects
my @these = TheOneTrue::Manager->get_these(); # returns These objects
it seems like an intriguing idea, but what headaches might one run
into with this approach?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
