Hello Jim,
Is it possible to try this query out with the latest GA release 10.2.1.6 ?
http://db.apache.org/derby/derby_downloads.html#Latest+Official+Release
There have been some fixes in the related code generation areas for 10.2:
DERBY-766, DERBY-1714 etc.
Also, can post the schema that can
Hi Rajesh,
I am not using one database from the cliet and the datasource.
Yes , I understand for Embedded a Derby database can be booted only
from a
single JVM.
And that cause the problem for my errors(I have later found out)
But according to my
Hi everyone,
I thought the problem would go away if I gave Derby a better written query,
so I fixed my query generator to be a bit smarter. Unfortunately, I still
get a stack overflow error. Here's the new query:
ij(SAMPLEBASE)> select count(*) from time where time.id in (select time.id
from
Hi All,
Is it possible to give me a time frame for when DERBY-1204 is likely to be
fixed.
Thanks,
Peter.
_
Advertisement: 110,000+ cars with the click of a mouse at carsales.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F
Suraj Batuwana wrote:
Hi ,
I have received following server side and client side(inside junit test
classes) when I am running my application's nightly build for Websphere
6.0.2.5 with derby10.2.1.6. I have used IBM JDK 1.4.2 which comes with my
Websphere
I have used the org.apache.derby.jdbc
Any reason why I should get a stack overflow error with the following query?
Yes, I know the query is a bit odd... it's not hand-written. The query
generator could be optimized. Nevertheless... is the stack overflow here
considered a bug or a limitation? If limitation, what specifically is the
Thanks for all of your replies, but I'm not saying that we have a bug
here. It's just that for large IN clauses there are many levels of
recursive calls in the server.
This reminded me of the other runtime memory limit, the heap. And so I
asked for some best practices on sizing these.
Regard
