Diff not working from command line

Hi,

I am evaluating liquibase to diff two databases. The goal is to have one master database and find missing or changed columns in the target database. Ideally the plan is, to emit SQL code to bring the target up to date. Both databases run on the same database system which is Sybase ASE 15. I changed the column length of a varchar column (enlarged) and created a new table in the master database. Then I ran liquibase with either jconn3.jar from Sybase itself and as this showed no differences I changed the JDBC driver to be jTDS. Either way no differences were detected and reported. The following output is generated:

0 [hostA]/liquibase|> ./liquibase --driver=net.sourceforge.jtds.jdbc.Driver --url=jdbc:jtds:sybase://hostA:8300/target --username=user --password=password diff --referenceUrl=jdbc:sybase:Tds:hostB:8305/master --referenceUsername=user --referencePassword=password
Liquibase Home is not set.
Liquibase Home: /liquibase
INFO 2/2/11 5:35 PM:liquibase: Reading tables for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading views for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading foreign keys for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading primary keys for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading columns for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading unique constraints for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading indexes for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Sequences not supported for master @ jdbc:sybase:Tds:hostB:8305/master …
INFO 2/2/11 5:35 PM:liquibase: Reading tables for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading views for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading foreign keys for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading primary keys for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading columns for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading unique constraints for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Reading indexes for target @ jdbc:jtds:sybase://hostA:8300/target …
INFO 2/2/11 5:35 PM:liquibase: Sequences not supported for target @ jdbc:jtds:sybase://hostA:8300/target …

Diff Results:
Reference Database: master @ jdbc:sybase:Tds:hostB:8305/master
Target Database: target @ jdbc:jtds:sybase://hostA:8300/target
Product Name:
    Reference:  ‘Adaptive Server Enterprise’
    Target: ‘ASE’
Product Version:
    Reference:  ‘Adaptive Server Enterprise/15.0.3/EBF 17156 ESD#3/P/Sun_svr4/OS 5.8/ase1503/2726/64-bit/FBO/Fri Feb  5 05:26:23 2010’
    Target: ‘15.0’
Missing Tables: NONE
Unexpected Tables: NONE
Missing Views: NONE
Unexpected Views: NONE
Changed Views: NONE
Missing Columns: NONE
Unexpected Columns: NONE
Changed Columns: NONE
Missing Foreign Keys: NONE
Unexpected Foreign Keys: NONE
Missing Primary Keys: NONE
Unexpected Primary Keys: NONE
Unexpected Unique Constraints: NONE
Missing Unique Constraints: NONE
Missing Indexes: NONE
Unexpected Indexes: NONE
Missing Sequences: NONE
Unexpected Sequences: NONE
Liquibase ‘diff’ Successful

Did I forget any essential flag to get it working? Any help welcome.

Best regards
renos

Unfortunately, it is a limitation of the diff tool.  Currently it does not check column size.  The plan is to focus on diff support as part of 2.1.

Nathan

Any timeline as to when 2.1 is planned for release?

Btw, I really only care about checking the column size and not the other features like stored procedures, etc. planed for 2.1.   Columns size seems pretty basic.  Maybe it could be added to 2.0.4 or another 2.0.x release…

Supporting the different column sizes ends up changing enough that it is worth including in with a bunch of other changes. There have been a couple of other status questions lately, so I’m going to do a general status update post on blog.liquibase.org today or this weekend. 


The short version is “working hard on a 3.0 release, but not ready for a few weeks at least”.


Nathan