Problems with addNotNullConstraint in MySQL

General Discussion
1

The problem seems to be in JIRA in order to the bug is fixed.

2

Great, thank you :wink:

3


I’ve the following changeset:


    [INFO] Error setting up or running Liquibase: Migration failed for change set src/main/resources/db.changelog-1.0.xml::add-new-column-changed_default_admin_password::smontes:
        Reason: liquibase.exception.DatabaseException: Error executing SQL UPDATE configuration SET changed_default_admin_password = ‘FALSE’ WHERE changed_default_admin_password IS NULL:
              Caused By: Error executing SQL UPDATE configuration SET changed_default_admin_password = ‘FALSE’ WHERE changed_default_admin_password IS NULL:
              Caused By: Incorrect integer value: ‘FALSE’ for column ‘changed_default_admin_password’ at row 1


    LiquiBase is creating the new column as tinyint(1) and then it doesn’t accept FALSE as value.

    This is only happens in MySQL while in PostgreSQL it’s working fine.

    Any idea about the possible problem?

    Thanks,
      Rego

4

The problem seems to be in JIRA in order to the bug is fixed.

5

Proposed patch to fix the problem in JIRA: http://liquibase.jira.com/browse/CORE-858

6

Thanks for the patch, I’ll look at getting it applied.


Nathan