Re: JDBC driver question

[Jonathan Eric Miller]

One of the other issues regarding the lack of descriptive error messages in 
the JDBC exceptions is that the ij query tool appears to use that same text, 
so, if you're using the higher-level tool and run into an exception, you're 
left scratching your head.

Jon
----- Original Message ----- 
From: "Jonathan Eric Miller" <[EMAIL PROTECTED]>
To: "Derby Discussion" <derby-user@db.apache.org>
Sent: Thursday, January 20, 2005 10:33 AM
Subject: Re: JDBC driver question


Thanks to all that responded. I'll give your suggestions a try. I was able 
to resolve the specific issue that I was having. Basically, I generated my 
database schema using Hibernate and it didn't create my id field with an 
IDENTITY like I thought it did. I corrected that, and now it seems to work 
fine.

I think that will be a definite plus when IBM releases source code for the 
JDBC driver as well. The non-descript exception messages are something 
that I ran into right off the bat. If those could be fixed up, I think 
that would help a lot in terms of ease of use/development. Or, if nothing 
else, if the error codes were at least listed in a document that comes 
with the driver. Does anyone know if there is such a document somewhere? I 
noticed in the Java API Specification documentation that the codes are 
XOpen or SQL 99. There are also vendor specific codes.

Jon