Comments on: Unit Testing Hibernate Code With Derby http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/ Subhash's Tech Log Thu, 23 Jun 2011 14:23:23 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Parth http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/comment-page-1/#comment-1379 Parth Thu, 23 Dec 2010 15:48:57 +0000 http://indiwiz.com/?p=138#comment-1379 Not working for me... getting NullPointer Exception at session.save(object); Not working for me… getting NullPointer Exception at session.save(object);

]]> By: BP-2000 http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/comment-page-1/#comment-982 BP-2000 Thu, 02 Dec 2010 13:57:02 +0000 http://indiwiz.com/?p=138#comment-982 Hi, I'm wondering how you would make Derby create and alter the tables given a specific DDL/DML instead of having Hibernate create the tables. That is, I would like use in the persistence.xml and have the tables created from a certain DDL (by Derby). My current problem is that in production I have a separate DDL and DML and only let Hibernate validate the schema; but I also want to use those DDL/DML in my unit tests instead of having Hibernate create the tables in a manner different from the DDL/DML. Hi,
I’m wondering how you would make Derby create and alter the tables given a specific DDL/DML instead of having Hibernate create the tables. That is, I would like use in the persistence.xml and have the tables created from a certain DDL (by Derby).

My current problem is that in production I have a separate DDL and DML and only let Hibernate validate the schema; but I also want to use those DDL/DML in my unit tests instead of having Hibernate create the tables in a manner different from the DDL/DML.

]]> By: chas66 http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/comment-page-1/#comment-26 chas66 Sun, 10 May 2009 01:20:11 +0000 http://indiwiz.com/?p=138#comment-26 Hi, I'm not sure what kind of testing you're talking about, but you may want to check out the unitils project at http://www.unitils.org/summary.html . Among other things using it enables easy setup and teardown of databases for testing. On a similar note, another project I've recently discovered and found very useful is Liquibase at http://www.liquibase.org/ This gives robust change managment of databases schemas etc rather than relying on Hibernate hbm2ddl.auto, which does not help with versioning or upgrades of the persistence layer. Cheers! Chas66 Hi,
I’m not sure what kind of testing you’re talking about, but you may want to check out the unitils project at http://www.unitils.org/summary.html . Among other things using it enables easy setup and teardown of databases for testing. On a similar note, another project I’ve recently discovered and found very useful is Liquibase at http://www.liquibase.org/ This gives robust change managment of databases schemas etc rather than relying on Hibernate hbm2ddl.auto, which does not help with versioning or upgrades of the persistence layer.
Cheers!
Chas66

]]> By: subwiz http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/comment-page-1/#comment-24 subwiz Sat, 24 Jan 2009 14:27:06 +0000 http://indiwiz.com/?p=138#comment-24 We did not face this as limitation in our test code. Our actual code was on Oracle, and the test in Derby. The .hbm.xml had the following for the primary key field in Oracle: <generator class="sequence"> <param name="sequence">sequence_name</param> </generator> and this for Derby: <generator class="identity"/> We did not face this as limitation in our test code. Our actual code was on Oracle, and the test in Derby. The .hbm.xml had the following for the primary key field in Oracle:

<generator class="sequence">
<param name="sequence">sequence_name</param>
</generator>

and this for Derby:

<generator class="identity"/>

]]> By: Binil Thomas http://indiwiz.com/2009/01/05/unit-testing-hibernate-code-with-derby/comment-page-1/#comment-25 Binil Thomas Tue, 20 Jan 2009 04:02:47 +0000 http://indiwiz.com/?p=138#comment-25 The most disappointing thing about Derby though is the lack of sequences. See https://issues.apache.org/jira/browse/DERBY-712. The most disappointing thing about Derby though is the lack of sequences. See https://issues.apache.org/jira/browse/DERBY-712.

]]>