generateChangeLog generates too many 'constraints'
Description
Environment
PostgeSQL 9.3.5.1, OS X 10.9.5, Maven 3.2.1, Java 8, Spring Boot 1.1.7
Activity
Show:
Nathan Voxland March 14, 2016 at 4:40 PM
Fixed for 3.5.0

David B Malkovsky September 22, 2015 at 12:49 PM
This issue appears to be directly related to issues https://liquibase.jira.com/browse/CORE-2439#icft=CORE-2439 and CORE-2277.
Fixed
Reporter
Matt Raible
Matt RaibleComponents
Fix versions
Affects versions
Priority
Created October 4, 2014 at 6:52 PM
Updated March 14, 2016 at 4:40 PM
Resolved March 14, 2016 at 4:40 PM
When I run the generateChangeLog command against a Hibernate-generated PostgreSQL database, I get a YAML file with the following contents. Notice that there's two 'constraints', when the correct behavior seems to be one.
databaseChangeLog: changeSet: id: 1412448028962-1 author: mraible (generated) changes: - createSequence: sequenceName: hibernate_sequence changeSet: id: 1412448028962-2 author: mraible (generated) changes: - createTable: columns: - column: constraints: constraints: nullable: false name: id type: VARCHAR(255) - column: name: content type: TEXT
If I change it from:
- column: constraints: constraints: nullable: false
to:
- column: constraints: nullable: false
then it seems to work correctly. Using Liquibase with Spring Boot.