|The stupid question is the question not asked|
What's the best module to stop mixing SQL with Perl?by Withigo (Friar)
|on Sep 08, 2006 at 19:56 UTC||Need Help??|
Withigo has asked for the
wisdom of the Perl Monks concerning the following question:
I am encountering the well known problem of mixing SQL and Perl in a huge codebase, and am looking for some advice about some alternatives to simplify or abstract my code.
Let's say I have a thousand subs, each of which has multiple handcrafted SQL queries which are doing complex joins and subselects on 4 or more other tables. It's a nightmare to alter to say the least.
But I would like to avoid the performance hits that Class::DBI and DBIx::Class impose. (I'm assuming DBIx::Class is now more popular/prefered to Class::DBI?). I like that plain DBI is 10-50 times faster.
And after accounting for the complex joins, subselects and where conditions I don't think representing each table as a single class will model very well to my code. I think for the OO approach to fit my existing code, I would need a class that represents the composition of several tables, but I may be overlooking the full capabilities of DBIx::Class etc.
I am looking into using an SQL phrasebook to reduce and separate the SQL from perl, but there are several such modules on CPAN to choose from. Can anyone recommend the best modules that might be appropriate for my situation and make my code better?
I'm preferably looking for the modules that are the most popular, most used and most recent. I looked at these modules: