db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-216) expand largeCodeGen.java test
Date Sat, 06 May 2006 01:19:33 GMT
    [ http://issues.apache.org/jira/browse/DERBY-216?page=comments#action_12378176 ] 

Kathey Marsden commented on DERBY-216:

With revision 37644 I fixed the run to run differences and at that time the test passed with
both embedded and client on Windows.  I never tried on Linux.

With revision 377609 Dan was able to move the number of parameters in the in list query from
3400 to 97000 (amazing). I don't know if it passed with client at that time.

Raman's testing shows that client fails before 97000 with client.
Raman  what is the highest number it goes to with client and what is the error and stack trace
when it fails? In the test there is a  boolean PRINT_FAILURE_EXCEPTION  that you will have
to change to see the failure.

> 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:
For more information on JIRA, see:

View raw message