For databases managed by unitils, a different table is used to store information about the current status of the database. This table is called DBMAINTAIN_SCRIPTS and contains a record for every script that was executed. The next time you update your database, the DbMaintainer will fail because this table doesn't exist yet. The error message also contains the DDL for creating this table. You can make sure this table is created automatically by setting the property dbMaintainer.autoCreateExecutedScriptsTable to true.
The dbmaintainer no longer supports post-processing scripts configured using the property dbMaintainer.postProcessingScript.locations. Instead, you can define one or more directories relative to the scripts location that contain post-processing scripts using the property dbMaintainer.postProcessingScript.directoryName. By default, scripts inside the directory called 'postprocessing' are regarded as postprocessing scripts.
In 1.1-rc-2 we've made the migration of the DB_VERSION table more explicit. If a version table is found that uses the old structure, an exception is raised. The new structure should contain a column version_indexes instead of version_index.
The easiest way to migrate to the new version table structure, is to drop the old one and then recreate the new one using the create statement that was specified in the exception. If you then run your tests, it will re-create the unit test database from scratch (if enabled) and update the version table to the correct version. If you don't want to do this, you can also use the values of the old version record and use the value of the version_index column for the version_indexes column adding the indexes of the parent folders.
For example: suppose you have following scripts folder structure:
Suppose you have following scripts folder structure:
When migrating from Unitils 1.0 to 1.1-rc-1, following changes need to be made:
If you're using the DBMaintainer: In the first place, the property dbMaintainer.fileScriptSource.scripts.locations must be renamed to dbMaintainer.script.locations. We also advise you to read the section on automatic test database maintenance in the tutorial. The DBMaintainer has a lot of new features such as:
If you're using Unitils' hibernate integration:
@HibernateSessionFactory
protected Configuration createConfiguration() {
AnnotationConfiguration configuration = new AnnotationConfiguration();
configuration.loadConfig("hibernate.cfg.xml");
configuration.addAnnotatedClass(Person.class);
configuration.addAnnotatedClass(Car.class);
}
@HibernateSessionFactory
protected void createConfiguration(AnnotationConfiguration configuration) {
configuration.loadConfig("hibernate.cfg.xml");
configuration.addAnnotatedClass(Person.class);
configuration.addAnnotatedClass(Car.class);
}
If you're using JPA with hibernate, toplink or openjpa as persistence provider, then try out unitils' brand new JPA support for testing your persistence layer code!
When migrating from Unitils 1.0-rc-3 to 1.0-rc-4, following changes need to be made:
If no file name is specified for the @DataSet annotation, Unitils will no longer first look for a file named className.methodName.xml. It will only look for a file namedclassName.xml.
All uses of method-specific data sets must therefore be replaced by explicitily loading the data set file. So, suppose you have a method-specific data set named UserDAOTest.testFindByMinimalAge.xml, this will no longer be loaded in following example:
@DataSet
public class UserDAOTest extends UnitilsJUnit4 {
public void testFindByMinimalAge() {
}
}
@DataSet
public class UserDAOTest extends UnitilsJUnit4 {
@DataSet("UserDAOTest.testFindByMinimalAge.xml")
public void testFindByMinimalAge() {
}
}
When migrating from Unitils 1.0-rc-2 to 1.0-rc-3, following changes need to be made:
Rename the property database.schemaName to database.schemaNames in your configuration files. Multiple schema names may be specified, seperated by commas.
By default, the DBMaintainer will generate a number of XSDs describing your database instead of a DTD. If you want to continue using DTD's, you have to add the property org.unitils.dbmaintainer.structure.DataSetStructureGenerator.implClassName to your configuration with value org.unitils.dbmaintainer.structure.impl.DtdDataSetStructureGenerator. You also have to rename the property dtdGenerator.dtd.filename to dataSetStructureGenerator.dtd.filename. If you want to switch to using XSD's (recommended), specify the path to the directory where the XSD files should be put in the propertydataSetStructureGenerator.xsd.dirName.
If present in your config, the property dbMaintainer.cleanDb.tablesToPreserve needs to be renamed todbMaintainer.preserveDataOnly.tables. Table names may optionally be prefixed by their schema name. If all the tables from a certain database schema need to be preserved, you can specify this schema in dbMaintainer.preserveDataOnly.schemas.
dbMaintainer.clearDb.itemsToPreserve has been split up into multiple properties, for different types of database items. If you specified this property, move your items to preserve to one of the propertiesdbMaintainer.preserve.tables, dbMaintainer.preserve.views, dbMaintainer.preserve.synonyms or dbMaintainer.preserve.sequences. Identifiers may optionaly be prefixed by their schema name. If all the tables from a certain database schema need to be preserved, you can specify this schema indbMaintainer.preserve.schemas.