[ http://issues.apache.org/jira/browse/DERBY-815?page=all ]
Dyre Tjeldvoll updated DERBY-815: --------------------------------- Attachment: derby.log While converting AB's repro for the regression into a test (in the test harness) I discovered that the last execute triggers an unexpected exception in embedded mode (see the attached derby.log for details). I realize that to test the regression it is only necessary to run the test against the NetworkServer, but it shouldn't fail in embedded mode, should it? > Prevent unneeded object creation and excessive decoding in parseSQLDTA_work() > ----------------------------------------------------------------------------- > > Key: DERBY-815 > URL: http://issues.apache.org/jira/browse/DERBY-815 > Project: Derby > Type: Sub-task > Components: Network Server, Performance > Versions: 10.0.2.2, 10.1.1.0, 10.1.2.0, 10.1.1.1, 10.1.1.2, 10.1.2.1, > 10.1.3.0, 10.1.2.2 > Reporter: Knut Anders Hatlen > Priority: Minor > Fix For: 10.2.0.0 > Attachments: d815_regress.diff, d815_regress.java, d815_regress.stat, > d815_regress_derbyall_report.txt, derby-815.diff, derby-815.stat, derby.log, > derbyall_report.txt > > Reported by Kathey Marsden in DERBY-212: > In reviewing the Network Server Code and profiling there were several > areas that showed potential for providing performance > improvement. Functions that need optimizing to prevent unneeded object > creation and excessive decoding: parseSQLDTA_work() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira