If I'm writing programs that interface with a database then I'll almost always use Class::DBI. My reasons are largely pragmatic. Class::DBI has a large community of users and the support mailing list is full of clever people who are very happy to help out whenever I have problems.
Of course, it's not always true that the most popular option is necessarily the best, but when it comes to the selection of Perl modules I generally find that you don't go far wrong if you look at what the smart people at the heart of the community are using.
I don't know anyone who is using DBIx::Recordset or Ace, but I know lots of people who are using Class::DBI.
"The first rule of Perl club is you do not talk about
Perl club."
-- Chip Salzenberg
In reply to Re: object-relational Perl programming: best practice or compromise?
by davorg
in thread object-relational Perl programming: best practice or compromise?
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |