|No such thing as a small change|
Perl Catalyst and DBIx::Class best practice question.by perl_helper (Initiate)
|on Dec 12, 2008 at 10:40 UTC||Need Help??|
perl_helper has asked for the
wisdom of the Perl Monks concerning the following question:
I'm currently developing a Catalyst application using DBIx::Class as the ORM. I'm just wondering about the best practice for exception handling for the DBIx::Class.
Since I'm still in QA, currently I'm having a lot of that purple catalyst error screen whenever I did something wrong with the DBIx::Class(e.g creating a record with the wrong column name, or undefined as a parameter when searching for a record).
Of course we can't have that purple screen when we move it to production, so I'm just wondering if any monks here can give me an advice on how to tackle this problem?. I know that wrapping the DBIx::Class call with eval and catching it is one way, but it could be very exhaustive since there is so many places where we want to retrieve a record or create one.
Is there a more elegant solution to this?. I tried googling it as well as searching it in cpan but found no elegant solution.
Thanks for the help and advice that you can give me. Any link to a documentation will be much appreciated.Thanks,