Discussions
Categories
- 385.5K All Categories
- 4.9K Data
- 2.5K Big Data Appliance
- 2.4K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
SQLcl lb changeset labels and context not working properly?
Using SQLcl 21.4, it appears that the 'context' argument for Liquibase Changesets is being ignored. Changesets with a 'context' specified are applied no matter what context string is supplied in the update or updatesql command, or if no context string is supplied.
Using 'labels' is a little better. If label A is specified in the command, Changesets with labels A are applied and Changesets with labels B are not applied. But if no label is supplied is specified in the command, all the Changesets are applied, A, B and no label.
Is this the expected functionality?
Answers
-
OK, here is a simple example. The changelog has two changesets, each with a different 'labels' attribute, TEST and RELEASE.
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:n0="http://www.oracle.com/xml/ns/dbchangelog-ext"
xmlns:pro="http://www.liquibase.org/xml/ns/pro"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd
http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-4.6.xsd "
>
<changeSet author="Me" id="1" labels="RELEASE">
<comment>Create table 1</comment>
<createTable tableName="TABLE1">
<column name="test_column" type="varchar2(30 char)">
<constraints nullable="false"/>
</column>
</createTable>
</changeSet>
<changeSet author="Me" id="2" labels="TEST">
<comment>Create table 2</comment>
<createTable tableName="TABLE2">
<column name="test_column" type="varchar2(30 char)">
<constraints nullable="false"/>
</column>
</createTable>
</changeSet>
</databaseChangeLog>
If I run the following command in SQLcl, table2 is created:
lb update -changelog labels_test_changelog.xml -label TEST
I then rollback the update and run the command:
lb update -changelog labels_test_changelog.xml -label RELEASE
Now table1 gets created. All is going well so far.
If I rollback and then run the command:
lb update -changelog labels_test_changelog.xml
Both tables are created. Is this correct?
Now, rollback again and edit the changelog file and replace the two 'labels' with 'context', still with RELEASE and TEST.
Run the command:
lb update -changelog labels_test_changelog.xml -context TEST
Both tables are created in the database. This must be wrong.
Is it something I am doing wrong?
Ian Morgan
Hampshire UK