Constraints in Changelog

General Discussion
1

i am a new user if liquibase. i am using liquibase 1.9.5
When i generate changelog from a complete schema from db, the format of the constraints are not coming correctly. So the scripts generated from the change log has some errors in it when i try to run it in another schema. the sql for index is also not working when i create from the generated changelog. Can anyone tell me what may be the problem?? its very urgent…

2

I’m advising you use the trunk version of the liquibase: current 2.0-SNAPSHOT-RC6. Many bugs was fixed since 1.9.5 and in the diff functionality too.
Do you have an experience working with maven/svn?

3

yea i have a bit experience working in svn not maven.

4

Ok, let starting…

  1. Checkout the url http://liquibase.jira.com/svn/CORE/trunk
    svn co http://liquibase.jira.com/svn/CORE/trunk liquibase

  1. download a maven from http://maven.apache.org/ Follow the instructions on http://maven.apache.org/download.html
    To test installation run

      mvn --version
    I suggest you use the latest 3.0 version.

  2. goto liquibase folder

  3. run

      mvn install -Dmaven.test.skip.exec=true

would the build successfull, you’ll find liquibase\liquibase-core\target\liquibase-2.0-rc6-SNAPSHOT.jar.
This is an artifact what you need to use. Report any problem here.

Cheers, Oleg

5
Originally posted by: taranenko
I'm advising you use the trunk version of the liquibase: current 2.0-SNAPSHOT-RC6. Many bugs was fixed since 1.9.5 and in the diff functionality too. Do you have an experience working with maven/svn?
Yes, I agree with you taranenko that the trunk version of liquibase is better than the other one.pmp online training
6

Thanks. I used the version 2.0.5 rc, now the constraints are coming in correct format. But no default value is coming up for not null constraints. In 1.9.5 it was coming fine. Because of that i am having problem when i migrate from 1 schema to another. Can any1 suggest anything about this?

7

The default values should be coming in now

Nathan

8
Originally posted by: Nathan
The default values should be coming in now

Nathan

u mean with the new jar file, i should get the default value??

9

Yes, you should.  I committed a fix that will be in the RC6 release.  Hopefully tomorrow.

Nathan