LB 3.0.2 against MSSQL: Misbehaviour with dropAllDatabaseObjects

General Discussion
1

Hi all,

we have tested LB 3.0.2 (using Ant 1.8.2) with our scripts (in order to upgrade from LB 2.0.1) against MSSQL 2008 R2 (v10.50.4000.0) and found following strange behaviour:


    <dropAllDatabaseObjects

        driver="@{attribute.targetdb.driver}"

        classpathref=“classpath”

        url="@{attribute.targetdb.url}"

        username="@{attribute.targetdb.user}"

        password="@{attribute.targetdb.pwd}"

        defaultSchemaName="@{attribute.targetdb.schema}"

        schemas="@{attribute.targetdb.schema}"

        promptOnNonLocalDatabase="${liquibase.prompt.non.local.db}"

    />


[dropAllDatabaseObjects] INFO 01.08.13 08:36:liquibase: Successfully acquired change log lock

[dropAllDatabaseObjects] INFO 01.08.13 08:36:liquibase: Dropping Database Objects in schema: LB_TEST

[dropAllDatabaseObjects] INFO 01.08.13 08:36:liquibase: Creating database history table with name: [LB_TEST].[DATABASECHANGELOG]

[dropAllDatabaseObjects] INFO 01.08.13 08:36:liquibase: Successfully released change log lock

BUILD SUCCESSFUL


Ant macro attribute: @{attribute.targetdb.schema} = LB_TEST


After this “successful” run in the MSSQL schema LB_TEST is the DATABASECHANGELOGLOCK table dropped, and the content of DATABASECHANGELOG deleted, but nothing more! No other DB objects were dropped - as expected.


This script works fine with LB LB 2.0.1.


Kind regards,

Frank

2

Hi there,


we have tested LB 3.0.7and the above mentioned error doesn’t occure now any longer. 

 

Best regards,

Martin