in reply to Re: DBI::Sybase sometimes returns nothing, but does not generate an error -> how can I catch this?
in thread DBI::Sybase sometimes returns nothing, but does not generate an error -> how can I catch this?

Hi and thanks for the quick reply!

Actually, I had not set RaiseError before to be able to handle errors myself via the handle_db_error() function (as I use log4perl).

I was hoping setting RaiseError would eventually solve my problem, but it doesn't look like it does. Just dieing is not what I'm looking for ;-)

I have the strange feeling that this driver sometimes doesn't completely work.
I connect to a MSSQL database in the States and I'm in Germany. I have seen these errors where no error is reported a couple of times now.
Actually, the starnghe thing is that the resultset is empty although it shouldn't be, but no error is generated.

What I want to achieve at least is to find out if the resultset is empty before calling fetchall_hashref and assignning it to a variable.
Will try with eval, but have so far no idea how to prevent this error from showing up on stdout/stderr.

Cheers, Sven
  • Comment on Re^2: DBI::Sybase sometimes returns nothing, but does not generate an error -> how can I catch this?

In Section Seekers of Perl Wisdom