-Original Message-
From: Jeffrey Lichtman [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 3:15 PM
To: Derby Discussion
Subject: RE: Error 38000 with a stack overflow on recordset.next()?
Here's a potential workaround for your problem. I suspect it will
work, but I'
Here's a potential workaround for your problem. I suspect it will
work, but I'm not sure:
SELECT path from filesystemfiles where not exists
(select * from existingfiles where existingfiles.path =
filesystemfiles.path)
The query does the same thing as your original one with "not in", b
I believe I've figured out what's going on with this bug. It involves
an optimization to materialize subquery results in some cases. This
optimization works by creating a nested union of in-memory rows.
What's happening in this case is that the unions are nested so deep
that it gets a stack ove
>>Lastly, if you were to perform one test with the logStatementText TRUE
>>
>>
>
>
>
>>('derby.language.logStatementText=true') then post the derby.log we
>>would know what SQL statement Derby was chewing on when this problem
>>happens (the derby.log will get large so I would unset it after
Daniel Skiles wrote:
Hi Daniel -
It would be helpful to have the complete output from the derby sysinfo
command along with the JVM information supplied by 'java -version'. In
case you are not familiar with the sysinfo command it is:
java org.apache.derby.tools.sysinfo
Hi Daniel -
> It would be helpful to have the complete output from the derby sysinfo
> command along with the JVM information supplied by 'java -version'. In
> case you are not familiar with the sysinfo command it is:
> java org.apache.derby.tools.sysinfo
-- Java Information ---
Daniel Skiles wrote:
Daniel, any chance of posting a complete repro, so I can recreate the problem
to debug? I am also baffled by the stack trace and your description of your
program. Though your stack trace is useful, it would be lot more useful to
generate it with actual line numbers of the
Daniel, any chance of posting a complete repro, so I can recreate the
problem to debug? I am also baffled by the stack trace and your
description of your program. Though your stack trace is useful, it
would be lot more useful to generate it with actual line numbers of the
code. I can do this an
> The interesting thing about this is that the stack overflow is in
> UnionResultSet.openCore, yet what you describe here has nothing to do
> with unions. There's nothing in the language code that I know of that
> would introduce a UnionResultSet into any of these statements.
> I suspect the re
I start out by running the following prepared statement a few thousand
times:
INSERT into existingfiles (path, id) VALUES (?, ?)
Where path is a windows file path and id is an integer. I clear out the
parameters with clearParameters() after each insert and set them to new
values. Then I clos
> Hmmm, indeed it looks like it is looping in Derby code.
> Are you using a function or procedure? Can you post the query you are
> using, and if a function/procedure is involved the source of that? Any
> reproducible case would allow this to be fixed much quicker.
Dan.
Dan,
I start out by runnin
Daniel Skiles wrote:
> Dan,
> Thanks for the tip. The strange thing about this is that it seems to
> work fine if I use a different database, such as MS SQL Server or
> Oracle. While I wouldn't be surprised if it was my code causing the
> exception, the fact that it only happens with Derby makes
Daniel Skiles wrote:
> Hello All,
>
>
>
> I’m getting a I'm working on trying to embed Cloudscape into an app and
> every time I try to run the next() method on a result set I getting the
> following error:
>
> ERROR 38000: The exception 'java.lang.StackOverflowError' was thrown
> while evalu
Hello All,
I’m getting a I'm working on trying to
embed Cloudscape into an app and every time I try to run the next() method on a
result set I getting the following error:
ERROR 38000: The exception 'java.lang.StackOverflowError' was thrown while
evaluating an _expression_.
at
org
14 matches
Mail list logo
