On 3/8/06, John Siracusa <[EMAIL PROTECTED]> wrote:
> I looked into making such a thing a few times, but I'm still unclear about
> exactly what a Catalyst::Model::* class is expected to do. I don't see why
> you wouldn't just make a set of RDBO classes the usual way and then use them
> directly in your Catalyst app. What's the extra layer of Catalyst::Model::*
> for?
It's usually simple glue code and without it, things get less coherent.
You get one nice thing, though: $c->model('Artist') (where $c is the
Catalyst context object) returns the appropriate object for the
"Artist" model.
I think the main thing really is the Helper class provided along with
the models, which provide scaffolding so you're up and running as
quickly as possible using that model.
You can see the DBIx::Class example at the CPAN, it's pretty short and
simple code:
http://search.cpan.org/~bricas/Catalyst-Model-DBIC-0.13/
I think you'd probably be the best one to do this, since you'd know
exactly how RDBO should be used. With Catalyst scaffolding working for
RDBO I think this might bring more people to the RDBO world, since it
usually provides better performance than the other ORMs (IMO, it isn't
as widely used as the other ORMs because of a somewhat worse learning
curve, i.e. it's harder to learn).
Either way, I think that if you don't do it, sooner or later someone else will.
-Nilson Santos F. Jr.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
