Subject | Handling network errors |
---|---|
Author | maverickthunder |
Post date | 2008-08-13T00:09:19Z |
Hi,
Imagine an app attaches to a superserver database, starts a
transaction, make an update query and when the app is about to do
another query, the connection is broken and you receive an
isc_network_error error, connection lost or similar error...
... which is the correct way to shutdown the app?
Freeing the statement allocated with isc_dsql_allocate_statement
Then calling the isc_rollback_transaction
At last detaching from database?
Or directly detaching from database?
Because despite the connection is broken I think that one should make
that calls in order to free resources.
Best regards,
Mauro H. Leggieri
Imagine an app attaches to a superserver database, starts a
transaction, make an update query and when the app is about to do
another query, the connection is broken and you receive an
isc_network_error error, connection lost or similar error...
... which is the correct way to shutdown the app?
Freeing the statement allocated with isc_dsql_allocate_statement
Then calling the isc_rollback_transaction
At last detaching from database?
Or directly detaching from database?
Because despite the connection is broken I think that one should make
that calls in order to free resources.
Best regards,
Mauro H. Leggieri