I have doubts about the error handling methods to be applied. I am
trying to figure out how to catch any error while the Pro*C code is
being executed and to pass them upstream to the C++ layer. I must add
that the application is a never-ending server and therefore it must
not crash or even "exit()" upon failure.
Your comments/pointers are most appreciated and welcome.
TIA,
-Ramon
I have been using a couple of error catching statements:
- EXEC SQL WHENEVER SQLERROR DO sql_error("ORACLE error--\n");
- EXEC SQL WHENEVER NOT FOUND DO user_not_found();
and I was wondering if there is anything else that I could take
advantage of.
TIA,
-RFH
snip
> I have doubts about the error handling methods to be applied. I am
> trying to figure out how to catch any error while the Pro*C code is
> being executed and to pass them upstream to the C++ layer. I must add
> that the application is a never-ending server and therefore it must
> not crash or even "exit()" upon failure.
Umm ... what will your app do if the database it is connected to shuts
down?
I used the term "connected" loosely. I am not using a connection-
oriented protocol. Only when my server receives a request, it will
attempt to make a query to the Oracle server.
So, so answer your question, my app/server will simply say:
"The database is not available"
Without crashing or stopping.
-Ramon
There are some pointers to other places with suggestions here:
http://tkyte.blogspot.com/2008/01/why-do-people-do-this.html
jg
--
@home.com is bogus.
"I'd like to invite you to join my neighborhood network on
MerchantCircle. MerchantCircle helps me build stronger relationships
with the other businesses in our neighborhood. It's been a big help
for me to get referrals and to reach customers. It's exciting to see
our
local community take shape online, so I hope you'll connect with me
and Holistic Health & Medical Marijuana Dispensary! It's free to
join
and only takes a minute to sign up and connect." - What I get for
signing up with MerchantCircle.