Bugzilla – Full Text Bug Listing
| Summary: | EDT runtime exceptions don't report failing EGL statement location. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Hoffman <hoffmanp> | ||||||
| Component: | EDT | Assignee: | Project Inbox <edt.javagen-inbox> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | jeffdouglas, mheitz, smythew, svihovec | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 206210 [details]
library for loading database for test program
Here is exception.message returned with the exception. The line number mentioned here is the line number of a prepared SQL statement, not the EGL program. Syntax error: Encountered "," at line 1, column 21.: [sqlstate:42X01][sqlcode:30,000] *** This bug has been marked as a duplicate of bug 355170 *** |
Created attachment 206209 [details] Test case RBD has build option which directs that EGL exceptions should report the program and line number of the failing EGL statement when an exception occurs. This information is very helpful in resolving program bugs. Is there any way to do this in EDT? Attached example shows an exception reported without this information. If the test case wasn't written to log each step, it would be difficult to determined which SQL statement was in error.