Posted on by | Posted in Developer Blog | Tagged , , ,

In this post, we want to show you our Liquibase setup in a larger scale project that we've been developing for some time now.

Gather Requirements

First off, a bit more information about the project and the whole project environment:

  • The software developed in this project consists of different applications
  • Some applications use the same database, some use different ones
  • The software runs in multiple branch offices of a company

Posted on by | Posted in Developer Blog | Tagged , , ,

My team and I are currently working on an project we first started in early 2010. The application is in production since sometime late 2010 and there has been no active development except for minor enhancements and bugfixes since then. Even if our code, processes and tools were good in 2010 we've improved a lot since then. Working on my old projects is one of the occasions, where this becomes most evident.

Posted on by | Posted in Developer Blog, synyx Blog | Tagged , , ,

Recently, we started integrating Liquibase as a database schema migration tool into most of my team's projects, for both new from-scratch projects and already existing ones. Liquibase is great because it allows us to use an SCM tool like Git to manage different revisions of an applications database schema – or more specifically, the changes required to migrate the database schema from one revision to another.

Posted on by | Posted in Mobile Blog, Tutorial | Tagged , , , ,

In a recent project I encountered a problem with SQLite on android 2.1. On later versions, my code worked perfectly, but on 2.1 it crashed every time when trying to get a column from a cursor.

Here's the simplified code:

Posted on by | Posted in Developer Blog, Open Source Blog | Tagged , , , , ,

A while ago we wanted to store internationalisation for a project in database to allow (a subset of) users to create and update internationalisation using the application itself. When we searched the web for existing projects that allow to do this we did not find a good and ready to use solution. This is why we decided to write the code ourselves and make it available to others, especially since there was some public demand and it will probably not be shipped by SpringSource (check out Google for details).