On 19.06.2012 09:45, John English wrote:
On 05/06/2012 18:45, Dag H. Wanvik wrote:
Looks like a bug to me. The error XSCH4 Conglomerate could not be
created isn't being tested for in the Derby tests as far as I can
see. I also searched the bug tracker
On 20.06.2012 13:05, John English wrote:
On 20/06/2012 11:45, Kristian Waagan wrote:
Hi John,
I believe your assumptions are correct.
This is a bug in Derby where the temporary row holder, used to hold
generated keys, overflows and a temporary backing conglomerate is
attempted created with a
Hello,
It seems that running the following SQL statement results in an error in Derby,
while it's working fine in other DBs (such as Oracle or Sybase):
select
a as ColumnA,
null as ColumnB
from SomeTable
java.sql.SQLSyntaxErrorException: Syntax error: Encountered null at line 10,
column
On 6/20/12 9:55 AM, Pavel Bortnovskiy wrote:
Hello,
It seems that running the following SQL statement results in an error
in Derby, while it’s working fine in other DBs (such as Oracle or Sybase):
select
a as “ColumnA”,
null as “ColumnB”
from SomeTable
java.sql.SQLSyntaxErrorException:
Thank you so much, Rick, for your prompt response - it's very helpful.
It actually makes a lot of sense, esp. for my application.
Respectfully,
Pavel.
-Original Message-
From: Rick Hillegas [mailto:rick.hille...@oracle.com]
Sent: Wednesday, June 20, 2012 1:10 PM
To:
