[
https://issues.apache.org/jira/browse/DERBY-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-216:
-------------------------------------
Issue & fix info: [Newcomer]
Urgency: Normal
Labels: derby_triage10_8 (was: )
Marking newcomer, I think this should be doable.
Unfortunately, I've had trouble running the largeDataTests recently, but
assuming they can be made to work, more functionality could be added there.
Also, perhaps this issue can be split into further issues as some of the
functionality/testing desired has been implemented...
> expand largeCodeGen.java test
> -----------------------------
>
> Key: DERBY-216
> URL: https://issues.apache.org/jira/browse/DERBY-216
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.1.2.1
> Reporter: Kathey Marsden
> Labels: derby_triage10_8
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
