Start a new topic

select SQL that caused output / log when browsing

[This topic is migrated from our old forums. The original author name has been removed]

Hi, when a large sqlfile ran, it's close to impossible to find which SQL statement caused what log entry and what output grid belongs to which statement. It would be nice if the statement that caused the log entry of the output grid could be highlighted to make debugging this a bit easier. (and of course, I could have missed some hidden fruit) thanks, Ronald.

[This reply is migrated from our old forums.]

Re: select SQL that caused output / log when browsing
Ronald, Just to inform you that this is now solved in 9.0.4. http://www.dbvis.com/download/ Regards Roger
[This reply is migrated from our old forums.]

Re: select SQL that caused output / log when browsing
Ronald, We'll add a "Load SQL in New Editor" in next maintenance version. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: select SQL that caused output / log when browsing
Roger, thanks, I did not notice the icon as a useful item in the log. It is. Thanks. For loading the sql into the editor ... It's a pity that it loads the sql into the current editor, damaging the script. Load in new or specified editor would make this better. regards, Ronald.
[This reply is migrated from our old forums.]

Re: select SQL that caused output / log when browsing
Hi Ronald, To locate the matching SQL for a log entry just click the log entry icon. To reveal what SQL generated a specific result set, hover the mouse on the result set tab or right-click and select "Load SQL in Editor". It is currently not possible to locate and highlight the matching SQL from within a result set. Regards Roger