|laziness, impatience, and hubris|
Re: Class::DBI vs. DBIx::Classby rafl (Friar)
|on Jun 25, 2006 at 11:16 UTC||Need Help??|
I strongly suggest using DBIx::Class.
It learned a lot from the mistakes Class::DBI made and also has a vast amount of features Class::DBI doesn't have.
My favourite is the concept of ResultSets. For example can put together your queries piece by piece:
Now you can either iterate over the results of those two resultset..
.. or get a list of objects, representing rows, back..
.. or do further searches..
.. or do a related_searche to get a resultset associated with another table or view, which are somehow connected to the current resultset:
Note that SQL statements are only executed when it's actually needed, which makes DBIx::Class quite performant.
Even if DBIx::Class still misses some features one might expect (subqueries, triggers, ...) I think it's already quite stable and I use it for production in several places.