Continuous database integration with Liquibase

Software developer constantly need to implement and deploy a new version of an application. In issue 5-2017 of German Java magazine, our colleague Steffen Mall argues that simple and fast refactoring of a database model is one of the most important things in order to implement flexible business requirements.
Oliver Pitzschel
comment icon 0 12.04.2017

Generate database schema DDL script with JPA or Hibernate

Using an object-relational mapping framework like Hibernate disburdens developers from creating complex DDL scripts to setup an application’s database schema. However, in real life such scripts are still needed – at least for the DBA who forbids applications to alter database objects. This post shows how to easily generate the database schema DDL script without typing an SQL commands.
Andreas Günzel
comment icon 14.10.2016

Basics of continuous database integration with liquibase

Simple and fast refactoring of your database model is one of the most important things in order to implement flexible business requirements. Learn the basics of continuous database integration with liquibase. Liquibase supports tracking, managing and applying database schema changes. Feel the power and simplicity of liquibase.
Steffen Mall
comment icon 1 07.06.2016

Intermediate commit within transaction

For long running transactions sometimes we wish to commit a kind of intermediate result to the database. This sounds pretty simple – however, if we do not want to commit the current transaction, you may run into deadlock situations. In my current project I implemented a nice solution using JPA and EJB.
Andreas Günzel
comment icon 0 19.05.2016

Dynamically resolve Hibernate database dialect

When using Hibernate as JPA provider you need to tell the application which database vendor you are using. The classic approach is to set the property "hibernate.dialect". This works in most cases. However, I often have to cope with different database vendors serving the same datasource - depending on the current environment. A solution to this problem is to use a DialectResolver that dynamically detects the needed Hibernate dialect to talk to the database.
Andreas Günzel
comment icon 2 23.03.2016