Project

General

Profile

Bug #8183

debugging database module

Added by Ovidiu Maxiniuc 6 months ago. Updated 6 months ago.

Status:
WIP
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:

History

#1 Updated by Ovidiu Maxiniuc 6 months ago

This task is the place for discussions on how to do database debugging and develop tools for doing this optimally.

#2 Updated by Ovidiu Maxiniuc 6 months ago

  • Status changed from New to WIP

I created task branch 8183a and committed some of my code I have maintained for some time (r14914). It was designed not to be too aggressive and have minimal impact when compared to trunk revision. The main idea was to have the code in a separate class on which there are no dependencies, so it can be easily removed when deployed to customer (or added as a separate jar only when debugging).

Although each static method is individually documented, I will add some additional help on using them, especially on conditional breakpoints and tracing utilities.

#3 Updated by Greg Shah 6 months ago

This task should include an easy way to see a temp-table or permanent table's contents without having to do complex manpulations of internal FWD data structures.

If we don't have a similarly good way to view the contents of a single DMO, (temp or perm), then that also needs to be addressed. The bottom line: a debugger should have full access to viewing the underlying persistence content without being an expert in FWD.

#5 Updated by Eric Faulhaber 6 months ago

Code review 8183a/14914:

The changes look useful, but there is a security concern, in that these public methods can be used to execute arbitrary SQL. How do we protect access?

The debugging wiki will need updates as well, once we figure out the above.

Also available in: Atom PDF