DBMonitor feature

Discussion of open issues, suggestions and bugs regarding ODAC (Oracle Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
igleo
Posts: 6
Joined: Tue 04 Nov 2008 00:19

DBMonitor feature

Post by igleo » Tue 04 Nov 2008 23:54

It would be very convenient to copy from DBMonitor Params tab statement with params. So user can copy and test a procedure or select in debug environment.

hannes_a
Posts: 77
Joined: Sun 22 Jan 2006 20:44
Location: munic

Re: DBMonitor feature

Post by hannes_a » Wed 05 Nov 2008 13:26


igleo
Posts: 6
Joined: Tue 04 Nov 2008 00:19

Post by igleo » Wed 05 Nov 2008 17:59

yea, posted in 2006. I guess we could wait couple more years.... :(

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Thu 06 Nov 2008 09:04

We are not planning to release new version of DBMonitor in the nearest time. But we'll consider the possibility of adding this feature in the next version of DBMonitor.

jfudickar
Posts: 202
Joined: Fri 10 Mar 2006 13:03
Location: Oberursel / Germany

Post by jfudickar » Thu 06 Nov 2008 20:28

Hi Oleg,

please have a look at my old list of requests also :-)

1. Application
In the process list there should be an separate entry for each application instance.
Each time the application is restarted there should be a new entry.

Otherwise the debugging is realy awfull.

It would be nice to show the user and servername in additional columns.
When the application terminates and then is restarted

2. Live Status of Components
As i have written in the forum, every time a component is terminated this should be mentioned in the log.

3. Additional Columns
I would split the description column into the following columns:
Type
SQL
Params
Error

4. TDBMSPackage Statements
Show the name of the package in the list of components and not the TOraSQL String

5. Make the result list sortable and better also searchable.

6. Select Results
As also mentioned in the forum show each "net-traffic" of an select statement in the result list.
So every record block which is fetched (make this optional) and also the number of result records.

7. I have one component which creates and drops different TOraQueryComponents step by step. Each component has a separate name.
In the Component List only the entry of the first query is shown with the defined name. And the statements of all different queries are shown under the name of the first query.
Maybe you are looking for the address of the component and use this to identify the component.
This should be looked for in combination with point 2.
8. Allow to copy text from error tab to the clipboard .
9. Add the errormessages to the exported log-file also.

Any further comments from other users :-)

Greetings
Jens

Post Reply