Hello Kambiz, Hello Jeroen,
My colleague pointed me to your mails at the mailing list as we were also
interested in that topic. In datanucleus documentation see [1] I found a hook
that can be used. Please note that I implemented that yesterday, so it is not
well tested but the application starts and all integration tests are green.
In persistor_datanucleus.properties add this:
isis.persistor.datanucleus.impl.javax.jdo.PersistenceManagerFactoryClass=com.example.FlywayJdoPersistenceManagerFactory
and turn off the auto generation:
isis.persistor.datanucleus.impl.datanucleus.schema.autoCreateAll=false
Also I turned off validation because I had issues with LONGVARBINARY as HSQL
replaced it to VARBINARY which datanucleus was not very happy about that ;)
isis.persistor.datanucleus.impl.datanucleus.schema.validateAll=false
isis.persistor.datanucleus.impl.datanucleus.schema.validateTables=false
isis.persistor.datanucleus.impl.datanucleus.schema.validateColumns=false
isis.persistor.datanucleus.impl.datanucleus.schema.validateConstraints=false
Here the implementation of the class:
import org.datanucleus.api.jdo.JDOPersistenceManagerFactory;
import org.datanucleus.metadata.PersistenceUnitMetaData;
import org.flywaydb.core.Flyway;
public class FlywayJdoPersistenceManagerFactory extends
JDOPersistenceManagerFactory {
public FlywayJdoPersistenceManagerFactory() {
super();
}
public FlywayJdoPersistenceManagerFactory(final PersistenceUnitMetaData
pumd, final Map overrideProps) {
super(pumd, overrideProps);
migrateDatabase();
}
public FlywayJdoPersistenceManagerFactory(final Map props) {
super(props);
migrateDatabase();
}
private void migrateDatabase() {
//String driverName =
(String)this.getProperties().get("javax.jdo.option.ConnectionDriverName");
Flyway uses auto detection...
// String url =
(String)this.getProperties().get("javax.jdo.option.ConnectionURL"); don't use,
as the propertie names are changed during initialization of superclass
// String userName =
(String)this.getProperties().get("javax.jdo.option.ConnectionUserName");
// String password =
(String)this.getProperties().get("javax.jdo.option.ConnectionPassword");
try {
Flyway flyway = new Flyway();
flyway.setDataSource(this.getConnectionURL(),
this.getConnectionUserName(), this.getConnectionPassword());
flyway.migrate();
} catch (Exception e) {
e.printStackTrace();
}
}
}
Hope that helps you!
Regards Timothy
[1] http://www.datanucleus.org/products/datanucleus/jdo/pmf.html
>Hi Kambiz,
>
>There's currently not a nice hook that I can think of to execute Flyway
>migrations. I would create a separate "upgrade" mode to start Isis that
>bootstraps with an in-memory db and allows you to do the Flyway stuff. But
>Dan probably has other ideas ;-)
>
>I've looked into Flyway for exactly the same purpose but was not really
>enthousiast about it. What I disliked the most is that you have to maintain
>every single db change in scripts. For me, the domain model is the source
>and persistence should be derived from that. And Datanucleus does an
>excellent job in creating all database artifacts so I want to keep
>leveraging that.
>
>What we currently do (manually) is roughly this:
>1. stop Isis;
>2. drop all db constraints;
>3. apply db upgrade script (for the changes that cannot be handled by
>Datanucleus);
>4. start Isis;
>5. execute upgrade service (for programmatic changes).
>
>We are also trying to crack the nut on how to automate this but encounter a
>few hurdles and I am not sure if Flyway can tackle those:
>- we have applications that consist of multiple modules, each with its own
>db schema and that change independently and the application should
>orchestrate the right order of upgrading;
>- a lot of times data is migrated, even between schemas and we sometimes
>use temporary views to do a pre and post check;
>
>Any ideas are welcome.
>
>Cheers,
>
>Jeroen
______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
