Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 3.5.1
    • Fix versions: 3.5.4
    • Environment:

      PostgreSQL 9.3 on RHEL7

    • Sprint:

      Description

      On an empty PostgreSQL database (No tables).

      Running liquibase update on a changelog (attached) with includeAll directory with one changeset (attached) results in the following:

      Unexpected error running Liquibase: ERROR: relation "another_table" already exists Failed SQL: CREATE TABLE public.another_table (COLUMN1 TEXT)

      However, the table is created, and a row in databasechangelog exists:
      1474550333-1,xxx,/home/xxx/projects/liquibase/examples/changesets/changeset-1.0.xml,2016-09-23 14:52:12.594651,1,EXECUTED,7:a77a8f27c4a6adcbe231d135a56e6a33,createTable tableName=another_table,A sample change log,,3.5.1,,,4660332585

      Subsequent runs of same command result in:
      Unexpected error running Liquibase: ERROR: relation "another_table" already exists Failed SQL: CREATE TABLE public.another_table (COLUMN1 TEXT)

      Debug output of first and second runs are attached.

        Attachments

        1. changeAll.xml
          0.4 kB
        2. changeset-1.0.xml
          0.6 kB
        3. first.run
          14 kB
        4. second.run
          12 kB

          Activity

            People

            • Reporter:
              ajscam aaron scamehorn
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: