in reply to Class::DBI::AbstractSearch and SpeedyCGI

If you're not doing it already, trap errors with ALL queries. Set the RaiseError flag on your db handle, and then make all executes look like this, or with some other useful error handling:
... my $query_handle = $db_handle->prepare($query); eval { $query_handle->execute(); }; if ( $@ ) { confess "Query Error $DBI::errstr\nQuery: $query\n"; }
And if you are using Bind Params, dump them too.
I use the most powerful debugger available: print!

Replies are listed 'Best First'.
Re^2: Class::DBI::AbstractSearch and SpeedyCGI
by zigdon (Deacon) on Oct 04, 2005 at 10:51 UTC
    I would, and did, when I execute my own queries... But with CDBI, it's all done so many layers lower than my code, that I'm not even sure where the eventual execute happens! I do believe RaiseError is set though, since the code does die when the error occures.

    -- zigdon