Error Handling
Posted: Mon 03 Feb 2014 17:03
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
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