Yeah, well I started with Class::DBI... DBIx::Class allows you to chain relationships., which I am not sure DB::Rose does.

 We have a pretty elaborate schema.
But anyway... I am not switching. Maybe next project (we have long term plans to make a very normalized schema, and layer application views on top of it, but that is down the road a ways).


Ben

From: "Ron Savage" <[EMAIL PROTECTED]>
DBIx::Class: Errr, I would definitely have gone with Rose there...

Which are the advantages of Rose?

Just in case you can't find the msg I referred to in my previous post,
the very syhort answer is:
o Rose gives you a Perl-centric view of your data
o The other mechanisms are all - AFAICT - row-centric

In othr words, this means Rose effortlessly slips under Perl umbrella.
--
Ron Savage
[EMAIL PROTECTED]
http://savage.net.au/index.html



#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

--
Ben Hitz
Senior Scientific Programmer ** Saccharomyces Genome Database ** GO Consortium
Stanford University ** [EMAIL PROTECTED]




#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

Reply via email to