Can you provide the query? 1800 items in an IN clause? That doesn't sound right or efficient.
Why not use a subselect? > -----Original Message----- > From: Robert Enyedi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 14, 2006 9:51 AM > To: Derby Discussion > Subject: Large IN clause produces server error > > In the attached JUnit error log one can see that for an query containing > an IN clause with 1800 items, Derby generates the following error: > > java.sql.SQLException: Statement too complex. Try rewriting the query to > remove complexity. Eliminating many duplicate expressions or breaking up > the query and storing interim results in a temporary table can often > help resolve this error. SQLSTATE: XBCM4: Java class file format > limit(s) exceeded: method:e4 code_length (134022 > 65535) in generated > class org.apache.derby.exe.ac8dd747d7x010exe6b4x4757x0000000d8160183. > > If rewriting the query is not an option, what alternatives are there to > overcome this limitation? > > Regards, > Robert
