Page 1 of 2

DbMonitor 3 Strange behaviour

Posted: Sun 14 Feb 2010 17:46
by starhu
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

Posted: Mon 15 Feb 2010 08:18
by Dimon
Please try to use the latest MyDAC build (5.90.0.55) and the latest dbMonitor build (3.0.2).

Posted: Fri 19 Feb 2010 09:09
by Thomas J.
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

Posted: Fri 19 Feb 2010 13:09
by Dimon
I still can not reproduce the problem.
Please specify the exact version of Delphi you are using and version of DBMonitor.

Posted: Fri 19 Feb 2010 13:21
by Thomas J.
I'm using
C++2010 V.14.0.3615.26342
DBMonitor 3.0.2
MyDac 5.90.0.55
UniDac 3.00.0.6

Posted: Mon 22 Feb 2010 16:00
by Dimon
I still can't reproduce the problem. Please check, that TMySQLMonitor is activated on your form.
Also try to compose a small sample to demonstrate the problem and send it to dmitryg*devart*com.

Posted: Tue 23 Feb 2010 06:52
by Thomas J.
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.

Posted: Thu 25 Feb 2010 08:29
by Dimon
Unfortunately I still can't reproduce the problem. I will wait for your sample to demonstrate the problem.

Posted: Fri 26 Feb 2010 11:56
by Thomas J.
Right now I don't have a sample, but it seems to be that TFrame is the problem. So if a TQuery is in a TFrame nothing is logged.

Posted: Mon 01 Mar 2010 10:04
by Dimon
Please send me the sample to demonstrate the problem.

Posted: Tue 02 Mar 2010 09:44
by Thomas J.
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 ...

Posted: Wed 03 Mar 2010 12:56
by Dimon
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.

Posted: Thu 04 Mar 2010 16:08
by Thomas J.
Hi Dimon,

thanks for the answer, but which checkbox in the filter should I uncheck?

Thanks
Thomas

Posted: Fri 05 Mar 2010 13:02
by Dimon
You should uncheck the Pending checkbox in the "Event Filter" dialog.

Posted: Fri 05 Mar 2010 13:22
by Thomas J.
No, still no logging