Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

kaare (663)

kaare
  (email not shown publicly)

Journal of kaare (663)

Thursday April 26, 2007
05:41 AM

Scream, Bitch, Scream!

[ #33107 ]
I just spent 5 hours yesterday debugging, searching for a bug in a Catalyst/DBIC application. How life would be easier if DBIC would die screaming instead of just bailing out in silent mode.

Combined with Catalyst's very talkative error trace, I get tons and tons of nonsense, and no useful information. In this case I was told that the problem was that there was an earlier transaction with problems. Well doh! Not very interesting. Tell me why you die, please.

Another thing about DBIC seems to be that $schema is utterly useless after a failed txn_do. You can get a resultset, see the classname, resoultsource etc. But don't you dare! to find some data. Why? Well, I don't know.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If I had a dollar for every time I've wasted time digging around a non working site just to find that DBIC/Catalyst/Auth plugins failed to load some class but never griped about it, I'd be a rich man. I could be doing something wrong of course, but I always end up fighting DBIC/Catalyst/Authentication plugins in some way shape or form. Me thinks there is something wrong with error handling when combining more than one of those things together.