Fabrice Bonduelle
Member
Hello,
Currently, if a query failed and the EOracleError is not managed within an OnThreadError event, it seems that it is impossible to know which is the TOracleQuery that caused the failure if the EOracleError is only caught by the TApplication.OnException event.
Nevertheless, it would be interesting to have this information in this case.
Is an evolution planned to enhance the EOracleError exception by adding into this exception a pointer to the TOracleQuery that failed?
Thanks for your answer.
Currently, if a query failed and the EOracleError is not managed within an OnThreadError event, it seems that it is impossible to know which is the TOracleQuery that caused the failure if the EOracleError is only caught by the TApplication.OnException event.
Nevertheless, it would be interesting to have this information in this case.
Is an evolution planned to enhance the EOracleError exception by adding into this exception a pointer to the TOracleQuery that failed?
Thanks for your answer.