Re: Heap and stack size for Derby server

[Bryan Pendleton]

I don't think this is DERBY-47. DERBY-47 is the issue that the plan generated by an IN query is inefficient.

This issue is that a query with a large number of IN parameters fails to compile due to a stack overflow error.

Good point.

Is this issue already known, then? Or would it be helpful for Robert to
file a new Jira issue to track it?

thanks,

bryan