Dear users,
we are very keen to make UniDAC better. We invite you to tell us what you think. Let us know if you have any comments or suggestions about UniDAC. We encourage you to provide us with feedback using this page.
Devart development team
http://www.devart.com/
Welcome to UniDAC Feedback Page!
-
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53
Feature request
Hi,
I hope this is the right place for a feature request
I'm looking for an easy way to build up a log of all executed queries so I can see which part of the code could do with further optimization.
The Debug property of TUniCustomDataset is very useful... however somewhat limited.
A new OnDebug event that gets called if Debug is True and Assigned(OnDebug) is True would enhance the debugging capabilties. Ideally the OnDebug event should be added to TUniCustomDataSet as well as to TUniConnection. If Debug is True and Assigned(OnDebug) is False, the current behaviour could be retained.
The OnDebug event for TUniConnection would allow for analysing all interaction with the database and should be called prior and after executing any query, starting, committing and rolling back a transaction, passing the SQL statement (if applicable) sent to the server as a string.
The OnDebug event for TUniCustomDataSet should be called prior and after executing a query passing the SQL statement sent to the server as a string.
What do you think?
kind regards,
Jan
I hope this is the right place for a feature request
I'm looking for an easy way to build up a log of all executed queries so I can see which part of the code could do with further optimization.
The Debug property of TUniCustomDataset is very useful... however somewhat limited.
A new OnDebug event that gets called if Debug is True and Assigned(OnDebug) is True would enhance the debugging capabilties. Ideally the OnDebug event should be added to TUniCustomDataSet as well as to TUniConnection. If Debug is True and Assigned(OnDebug) is False, the current behaviour could be retained.
The OnDebug event for TUniConnection would allow for analysing all interaction with the database and should be called prior and after executing any query, starting, committing and rolling back a transaction, passing the SQL statement (if applicable) sent to the server as a string.
The OnDebug event for TUniCustomDataSet should be called prior and after executing a query passing the SQL statement sent to the server as a string.
What do you think?
kind regards,
Jan
-
- Posts: 23
- Joined: Tue 23 Mar 2010 08:36
- Location: spain
- Contact:
Re: Welcome to UniDAC Feedback Page!
Hi,
.- Please update the help file, and try to be more explicit on the definitions.
.- Put some simple sample code into the help, that must be great. some times that be very usefully.
thanks
.- Please update the help file, and try to be more explicit on the definitions.
.- Put some simple sample code into the help, that must be great. some times that be very usefully.
thanks
Re: Welcome to UniDAC Feedback Page!
You can add any suggestions concerning our products at our UserVoice page: https://devart.uservoice.com/forums/104 ... components .