We are using Derby for our unit testing database. We just upgraded from 3.1rc2 to 3.1 final this morning and now get this error. Is there a workaround?

org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not insert: [com.webify.framework.triples.beans.VersionRecordBean]; uncategorized SQLException for SQL [insert into w_version (username, change_time, cl_gid, cl_lid, schema_ns_id, id) values (?, ?, ?, ?, ?, default)]; SQL
state [0A000]; error code [20000]; Feature not implemented: prepareStatement(String, String[]).; nested exception is org.apache.derby.impl.jdbc.EmbedSQLException: Feature not implemented: prepareStatement(String, String[]).
SQL Exception: Feature not implemented: prepareStatement(String, String[]).
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java)
at org.apache.derby.impl.jdbc.Util.notImplemented(Util.java)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConnection.java)
at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:4
18)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(Poo
lingDataSource.java:385)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.hibernate.util.GetGeneratedKeysHelper.prepareStatement(GetGeneratedKeysHelper.java:45
)
at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:435)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:93)

FWIW we are using Derby 10.1.1.0 and this is the Javadoc for the method throwing the exception. Note the throws clause.

http://db.apache.org/derby/javadoc/engi ... ang.String[])

then disable jdbc3 generated keys.

hibernate.jdbc.use_get_generated_keys false

Max, glad to see there is a workaround. Is this something that can or should go in the DerbyDialect?

its not dialect controllable at the moment afaik