Liquibase Incremental Database Changes

By -

LiquiBase is used for managing, tracking and applying database changes. It uses XML file for storing incremental changes to data base.These xml file stores both
Database structures(DDL) and codes.LiquiBase is an open source (LGPL) Library

The following are some of the features which attract LiquiBase a lot

1) It is Open Source
2) It is Database independent
3) Supports rolling back changes
4) Supports merging of changes from multiple developers


The XML file which contains input to Liquibase is called databaseChangeLog File.

The following is a example of a empty databaseChangeLog file

<databaseChangeLog
        xmlns="http://www.liquibase.org/xml/ns/dbchangelog/1.8"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog/1.8
        http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.8.xsd">
</databaseChangeLog>



The following fragment is a changeset, the following changeset defines a table called USERS with three columns.
  <changeSet author="Sidd" id="1.01">
    <comment>Users</comment>
          <createTable tableName="Users" >
            <column name="UsersID" type="BIGINT">
                    <constraints nullable="false" primaryKey="true" primaryKeyName="PK_Users"/>
             </column>
             <column name="USERNAME" type="VARCHAR(20)">
                    <constraints nullable="false"/>
             </column>
         <column name="USEREMAIL" type="VARCHAR(20)">
                <constraints nullable="false"/>
            </column>
    </createTable>
  </changeSet>



Liquibase can take this database changelog and create table automatically.



Getting started with LiquiBase takes four steps:

  1. Create a database change log file.
  2. Create a change set inside the change log file.
  3. Run the change set against a database via the command line or a build script.
  4. Verify the change in the database.

We can run Liquibase in two ways One is by firing commands from the console , or we can Use  Ant Tasks provided by Liquibase and call those task from Ant Build.
In the next post I will write how to work with Ant and Liquibase , probably with a example.

Comments

Post a Comment

Popular posts from this blog

Converting Java Map to String

By -
Java Collections framework, String manipulation etc is something that we often encounter in Development process. For processing collections (like checking null/empty, Intersection, Disjunction) We do have some of the very use full libraries. Some of the Collection related libraries are Apche Commons Collections and Google  Collections(Guava). Problem Use Case This article explains how to convert a Java Map to String(and vice versa) using different libraries and technique. One way is to use StringBuilder(Or String) and loop though the Map and build the String by applying some sort of separator ( for key:value and entry). Here we have to take care of the null value etc. Without Any Library If we want to convert the map to a String with key value separator and also individual entry seperator in the resulting String, we have to write code for that. For a simple Map, we have to iterate though the map, take care of the null values etc. Following is a sample to get String built
Read more

Difference between volatile and synchronized

By -
volatile is a field modifier, while synchronized modifies code blocks and methods. So we can specify three variations of a simple accessor using those two keywords: int i1; int geti1() {return i1;} volatile int i2; int geti2() {return i2;} int i3; synchronized int geti3() {return i3;} geti1() accesses the value currently stored in i1 in the current thread . Threads can have local copies of variables, and the data does not have to be the same as the data held in other threads. In particular, another thread may have updated i1 in it's thread, but the value in the current thread could be different from that updated value. In fact Java has the idea of a "main" memory, and this is the memory that holds the current "correct" value for variables. Threads can have their own copy of data for variables, and the thread copy can be different from the "main" memory. So in fact, it is possible for the "main"
Read more

Invoking EJB deployed on a remote machine

By -
Invoking EJB deployed on a remote machine In case we are calling remote ejb( ejb deployed on remote machines), The JNDI lookup might lookup like, Properties env = new Properties(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); env.put(Context.PROVIDER_URL, "XX.XXX.XX.XX:1099"); env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); Context ctx = new InitialContext(env); If we are calling local ejb then we can simply create InitialContext without any parameters. Like, Context ctx = new InitialContext();
Read more