Fixed LiquiBase issue with MySQL.

Execute the next SQL sentences in your database if you want to keep working with
your current database:

UPDATE databasechangelog
    SET md5sum='3:e32f913dd4429f4471ec850003dfc6d2'
    WHERE id='add-new-column-enable_critical_chain_support' AND
        author='jaragunde' AND
        filename='src/main/resources/db.changelog-1.0.xml';

UPDATE databasechangelog
    SET md5sum='3:71ae3b8d8998329d68e95d8ad2135745'
    WHERE id='use-capacity-instead-of-effort_duration-and-not_over_assignable' AND
        author='ogonzalez' AND
        filename='src/main/resources/db.changelog-1.0.xml';

FEA: ItEr68S04BugFixing
This commit is contained in:
Manuel Rego Casasnovas 2011-01-12 20:27:20 +01:00
parent 67a4164878
commit 8d5c9dfe1d

View file

@ -8,10 +8,12 @@
<changeSet id="add-new-column-enable_critical_chain_support" author="jaragunde">
<comment>Add new column enable_critical_chain_support with default value FALSE to configuration table</comment>
<addColumn tableName="configuration">
<column name="enable_critical_chain_support" type="BOOLEAN" />
<column name="enable_critical_chain_support" type="BOOLEAN">
<constraints nullable="false"/>
</column>
</addColumn>
<addDefaultValue tableName="configuration" columnName="enable_critical_chain_support"
defaultValue="FALSE" />
defaultValueBoolean="FALSE" />
</changeSet>
<changeSet id="use-capacity-instead-of-effort_duration-and-not_over_assignable" author="ogonzalez">
@ -20,7 +22,7 @@
<column name="allowed_extra_effort" type="INTEGER" defaultValue="NULL"/>
</addColumn>
<renameColumn tableName="calendar_exception_type" oldColumnName="duration"
newColumnName="standard_effort"/>
newColumnName="standard_effort" columnDataType="INTEGER"/>
<update tableName="calendar_exception_type">
<column name="allowed_extra_effort" valueNumeric="0" />
<where>not_assignable</where>