the largeCodeGen test needs to be expanded to include other cases that genreate large amounts of byte code.
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.