[ http://issues.apache.org/jira/browse/DERBY-216?page=comments#action_12364516 ]
Kathey Marsden commented on DERBY-216: -------------------------------------- I pulled the largeCodeGen test into the largeData suite. I suppressed the exception output for failed cases by default. It varies from run to run and jvm to jvm. There is a boolean PRINT_FAILURE_EXCEPTION that can be turned on for debugging. I am curious. Is there anyone out there that runs the largeData test from time to time? What are the system requirements? > expand largeCodeGen.java test > ----------------------------- > > Key: DERBY-216 > URL: http://issues.apache.org/jira/browse/DERBY-216 > Project: Derby > Type: Sub-task > Components: Test > Reporter: Kathey Marsden > > the largeCodeGen test needs to be expanded to include other cases that > genreate large amounts of byte code. > For example: > large in clause > large insert statement that inserts many rows > sql statements with large constant values > It is best if the verious tests just use a variable that can be bumped higher > and higher for testing and if individual cases are isolated. > Possible approaches, think of ways to make sql statements really big that > will take different code paths. > Look in the code for instances of statementNumHitLimit and create cases that > pass through that code. Those cases may pass but the hope is to get rid of > these calls in favor of splitting the code in a centralized way, so add the > tests to largeCodeGen even if they don't fail. > -- 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
