« New Catalyst Development Cycle, "SicilianButtercup" Starting Today! Contributors Needed! | Main | Perl Catalyst and the Crisis of Asynchronicity »



Feed You can follow this conversation by subscribing to the comment feed for this post.


That's great news, but I still look forward to 0.9 and better Moose integration.

I've recently spent longs hours trying to figure DBIx along with Moose. Actually - any ORM that would go well with Moose. Unfortunately neither go too well, and it's a pity DBIx is not Moose based, though the foretold version 0.9 is supposed to be.

It may be fast on ORM but becomes increasingly clumsy from developer point of view when dealing MOP-based projects. Such where one would typically have the DATA designed in base Moose classess and different persistence engines implemented in inherited classess. I mean the same data persisted over say DBI, SOAP and Excel stores.

There is currently no elegant way to tell DBIx to get the columns from inherited base Moose Class, which means you need to duplicate all such. Yeah, modules exists, the most recent 2 years old...

There's no way to keep the Moose-based relations from the base class into DBIx, and one would likely need tons of before/after triggers to get this working if you at all decide to go the automated way.

In the end of the day - it seems that a plain "no-smart" approach saves dev. time and brings more value into the project. It's a pity, since I love Moose and DBIx, but you cant' really get them along in your project.


The comments to this entry are closed.