This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I am currently getting some errors during a save operation. It would help a lot if the SQL-Statement that causes these problems would be included in the exception. I already have a logger for the sql-statements, but it only gives me the last working query. Regards, Dennis |
|
|
|
|
Thanks for the feedback Dennis, we'll discuss that idea :-) The only concern off the top of my head is that due to batching of queries it's conceiveable that there may be massive exception messages if an error is generated when pumping a sufficiently large batch of queries to the database. If you have any other feedback please do post it - in the lead up to the 4.0 release it is sometimes easier to implement things :-) Kind regards, John-Daniel Trask |
|
|
|
|
Hi, I just realized that all sql-queries (of the executed batch) are already written to the log. I just did not realize that and the last sql-statement was correct. None the less this feature would be nice, because looking into log-files takes its time and logging to console is awfully slow in VS. Regards, Dennis |
|
|
|
