Re^4: Moose + ORM

The issues of connecting to a database need to be resolved in a configurable flexible way
"The future of DBIx::Class talk" covers that syntax (32 minutes in) Maybe you could contribute to that.
Joins need to be solved?
If you just want an easy access to one table, maybe Tie::DBI is enough?

Comment on Re^4: Moose + ORM

Replies are listed 'Best First'.
Re^5: Moose + ORM by Anonymous Monk on Jul 24, 2009 at 13:45 UTC
I have #1 covered for my needs, but going forward as a CPAN module then yes, this needs to be solved. I'll check out the video. this can be solved by someone else, thank you. :) I personally think this is mostly a waste of time and can be handled by writing custom methods with optimized SQL. But when the day comes that someone actually solves this problem in a 100% reusable manner, I'll use it. :) this seems very unappealing -- the idea is to make a Moose role. Feel free to write an example that works with Moose if you really think I missed the point.	[reply]

Replies are listed 'Best First'.

Re^5: Moose + ORM
by Anonymous Monk on Jul 24, 2009 at 13:45 UTC

I have #1 covered for my needs, but going forward as a CPAN module then yes, this needs to be solved.
I'll check out the video.
this can be solved by someone else, thank you. :) I personally think this is mostly a waste of time and can be handled by writing custom methods with optimized SQL. But when the day comes that someone actually solves this problem in a 100% reusable manner, I'll use it. :)
this seems very unappealing -- the idea is to make a Moose role. Feel free to write an example that works with Moose if you really think I missed the point.