DbMonitor 3 Strange behaviour
DbMonitor 3 Strange behaviour
Hello,
After installing DbMonitor 3 - if there is an error in the Sql statement as "Select * from customersWhere f1=1", the dbMonitor doesn't show the error message like the previous version but shows the "pending" state and in the error tab it says: "Completed successfully."
In this way it is useless to me. I tried to use DbMonitor 2, but that can't connect to my applications any more.
I use MyDac 5.90.0.54.
Thank you
After installing DbMonitor 3 - if there is an error in the Sql statement as "Select * from customersWhere f1=1", the dbMonitor doesn't show the error message like the previous version but shows the "pending" state and in the error tab it says: "Completed successfully."
In this way it is useless to me. I tried to use DbMonitor 2, but that can't connect to my applications any more.
I use MyDac 5.90.0.54.
Thank you
I have the problem, that some statements are not logged at all.
This behavior I didn't saw in the last version.
It seems that statements which take more then normal have the problem.
In the DBMonitor is only written "MyDAC monitoring is started"
But I don't stop the debugging and if click 10 times on a refresh button in my application which loads the data again. The DBMonitor shows 10 times
"MyDAC monitoring is started"
Also if a query have an error nothing is shown only "MyDAC monitoring is started"
This is bad for checking errors in statements if you work with macros.
Thanks
Thomas
This behavior I didn't saw in the last version.
It seems that statements which take more then normal have the problem.
In the DBMonitor is only written "MyDAC monitoring is started"
But I don't stop the debugging and if click 10 times on a refresh button in my application which loads the data again. The DBMonitor shows 10 times
"MyDAC monitoring is started"
Also if a query have an error nothing is shown only "MyDAC monitoring is started"
This is bad for checking errors in statements if you work with macros.
Thanks
Thomas
I have only one TMySQLMonitor and this is the main data module.
I don't know if I can create a small sample.
But I will try ...
Try also to create a small sample using in your query UNION, FUNCTION and Views with MACROS and a long statement.
This is the case of these statements which are not logged or restart the monitor.
I don't know if I can create a small sample.
But I will try ...
Try also to create a small sample using in your query UNION, FUNCTION and Views with MACROS and a long statement.
This is the case of these statements which are not logged or restart the monitor.
Please download the file
www.cratemaker.de/Download/DbMonitor.zip
You will find a video, source files and a script for creating the tables.
I don't know if you can reproduce the problem also with empty tables.
So let me know ...
www.cratemaker.de/Download/DbMonitor.zip
You will find a video, source files and a script for creating the tables.
I don't know if you can reproduce the problem also with empty tables.
So let me know ...
The point is that Event status is Pending when an event is not finished yet. This situation occurs when a SQL query is being executed for a long period of time and client have not received any answer from SQL server yet.
You can uncheck the checkbox in the "Event Filter" dialog to exclude the event with the corresponding status from the log.
You can uncheck the checkbox in the "Event Filter" dialog to exclude the event with the corresponding status from the log.