NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Depends on what you're trying to do (Score:1)
Are you trying to abstract away your database? Stop right there. I'd lay odds that you're making a mistake of some sort.
Are you trying to do complex reporting? If so then an ORM is the wrong tool. If you're doing complex reporting, you want the full power of SQL. More than that, you want to have access to all of those special features your database supports that may not be widespread. If you're using postgres, their implementation of temp tables is wonderful. If you're using Oracle you get useless temp tables, but you should definitely learn your analytic queries. And so on.
Personally I do a lot of reporting so I don't use an ORM for any of that. But when I wanted to add tracking of who called what report with what parameters and how long it took, I immediately reached for Rose::DB. Which is only used for recording that information.
Reply to This