Thank you for your hint.
I've done the logging test you suggested.
3.1.1:
[30 Jul 2014 07:14:57,247] main DEBUG de.medav.dmf.server.base.MARServer.Container.LiquibaseService.liquibase - liquibase/db-changes.xml: liquibase/db-changes-4.4.xml::4.4.0-4c::tins: Computed checksum for changeAutoincrementValue:[] as 78fb688dce3de0e48421a8933c935ab3
3.2.2:
[30 Jul 2014 07:18:11,518] main DEBUG de.medav.dmf.server.base.MARServer.Container.LiquibaseService.liquibase - liquibase/db-changes.xml: liquibase/db-changes-4.4.xml::4.4.0-4c::tins: Computed checksum for changeAutoincrementValue:[
columnName="Id_Language"
tableName="mar_language"
] as b28775d91b0587713c6dbfd7b6a1ac9b
the correlating changeset:
<changeSet id="4.4.0-4c" author="tins" dbms="${autoIncrementDBMS}">
<comment>set autoincrement value to the maximum of column + 1 or the passed minValue</comment>
<ext:changeAutoincrementValue tableName="mar_language" columnName="Id_Language" minValue="1000000" />
</changeSet>
Seeing the debug log, none XML-attributes of the changeset have been considered for the checksum with the 3.1.1 version of the extension, whereas the string attributes/values are included in the 3.2.2 versions (why are the BigInteger-defined "minValue" attribute and value not included in the checksum of 3.2.2?).
What are the options to fix this now? I won't be able to get direct access to all the databases the changes have been run onto. I'm not sure if the "runOnChange" (or whatever the changeset-option is called) is a good idea either.
As stated in the original post, die extension used has been changed, I attach the 2 change-class versions (as a zip, as only one attachment is allowed).
I've done the logging test you suggested.
3.1.1:
[30 Jul 2014 07:14:57,247] main DEBUG de.medav.dmf.server.base.MARServer.Container.LiquibaseService.liquibase - liquibase/db-changes.xml: liquibase/db-changes-4.4.xml::4.4.0-4c::tins: Computed checksum for changeAutoincrementValue:[] as 78fb688dce3de0e48421a8933c935ab3
3.2.2:
[30 Jul 2014 07:18:11,518] main DEBUG de.medav.dmf.server.base.MARServer.Container.LiquibaseService.liquibase - liquibase/db-changes.xml: liquibase/db-changes-4.4.xml::4.4.0-4c::tins: Computed checksum for changeAutoincrementValue:[
columnName="Id_Language"
tableName="mar_language"
] as b28775d91b0587713c6dbfd7b6a1ac9b
the correlating changeset:
<changeSet id="4.4.0-4c" author="tins" dbms="${autoIncrementDBMS}">
<comment>set autoincrement value to the maximum of column + 1 or the passed minValue</comment>
<ext:changeAutoincrementValue tableName="mar_language" columnName="Id_Language" minValue="1000000" />
</changeSet>
Seeing the debug log, none XML-attributes of the changeset have been considered for the checksum with the 3.1.1 version of the extension, whereas the string attributes/values are included in the 3.2.2 versions (why are the BigInteger-defined "minValue" attribute and value not included in the checksum of 3.2.2?).
What are the options to fix this now? I won't be able to get direct access to all the databases the changes have been run onto. I'm not sure if the "runOnChange" (or whatever the changeset-option is called) is a good idea either.
As stated in the original post, die extension used has been changed, I attach the 2 change-class versions (as a zip, as only one attachment is allowed).