Page 1 of 1

Error Handling

Posted: Mon 03 Feb 2014 17:03
by Ekki
Hi,

I'm iterating thru a list of tables. Some of them may do not exist for a specific Schema.
I catch this with an exception. So far so good.

My issue however is: in case of such an exception, immediate sub-sequent calls fail. I can see in the DBMonitor that these calls are causing errors, mostly in the select statement, sometimes even in the open connection call. If I do comment-out the calls to the missing tables, all and everything works just great.

How can I handle the non-existing tables properly? Alternatively, can I check their existance before?

I tried to close the connection in the Exception block, no difference.

Thx ia,

Ekki

Re: Error Handling

Posted: Tue 04 Feb 2014 16:14
by Shalex
Ekki wrote:My issue however is: in case of such an exception, immediate sub-sequent calls fail. I can see in the DBMonitor that these calls are causing errors, mostly in the select statement, sometimes even in the open connection call. If I do comment-out the calls to the missing tables, all and everything works just great.
Please send us a small test project for reproducing the problem. Also specify the exact error(s) you are getting with its call stack.

Re: Error Handling

Posted: Mon 30 Jun 2014 11:58
by Ekki
Hi,

just uploaded the latest releases and still face this issue:

If I try to access a table not available in the database, I get an exception and see an error in the DB Monitor. So far so good. But the sub sequently following DB call fails although it normally would work.

Can u pls help?

Ekki

Re: Error Handling

Posted: Mon 30 Jun 2014 13:24
by Shalex
Ekki wrote:But the sub sequently following DB call fails although it normally would work.
1. Specify the exact text of the error you are getting and its stack trace.
2. Please send us a small test project for reproducing the problem.