Thomas Dudziak wrote: > While sitting here with Jean at the Hackathon and adding support for > Derby to OJB, I stumbled across a strange exception that might perhaps > be a bug. In short, OJB generates some SQL like this (don't ask): > > SELECT A0.TASK_ID,A0.PERSON_ID,A0.PROJECT_ID,A0.TASKNAME FROM TASK A0 > WHERE (A0.PERSON_ID = ?) AND A0.PROJECT_ID = ? OR ((A0.PERSON_ID = ?) > AND A0.PROJECT_ID = ?) OR ((A0.PERSON_ID = ?) AND A0.PROJECT_ID = ?) > OR ((A0.PERSON_ID = ?) AND A0.PROJECT_ID = ?) OR ((A0.PERSON_ID = ?) > AND A0.PROJECT_ID = ?) OR ((A0.PERSON_ID = ?) AND A0.PROJECT_ID = ?)
This is the same as DERBY-732 http://issues.apache.org/jira/browse/DERBY-732 There have been some fixes to up the limit in the trunk, see the sub-task list for 732. Dan.
