DBIx::Class (DBIC) is generally preferred [citation needed] over Class::DBI (CDBI) for the last few years; speed and flexibility the main reasons.
You can search the monastery for quite a few nodes discussing these kits and several others worth considering; Perl ORM comparison (Class::DBI vs. DBIx::Class vs. Rose::DB::Object); google:site:perlmonks.org dbic cdbi.
With DBIC there is not really an impedance mismatch because it has the meta-considerations of records and record sets (Results/ResultSets in DBIC parlance) split nicely and each encapsulates the proper layers like engine and SQL generation. These things have steep learning curves but once you get the hang of them they make dealing with data and databases trivial, testable, flexible, perly, and largely self-documenting [citation needed].
In reply to Re: Why use an OO -> SQL mapper module?
by Your Mother
in thread Why use an OO -> SQL mapper module?
by MyMonkName
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |