Quantcast
Channel: Liquibase Forums
Viewing all articles
Browse latest Browse all 2993

Re : Extension migration validation issue 3.1.1 -> 3.2.2

$
0
0
Thank you for your response, the validChecksum tag seems to be a good alternative.

I'd like to discuss an issue that was mentioned in my last post here:

xxx: Computed checksum for changeAutoincrementValue:[
    columnName="xxx"
    tableName="xxx"
] as xxx

was the log entry for one examplary changeSet, the changeSet however requires *3* attributes, the "minValue" field was not considered in the checksum calculation (it is a BigInteger member in constrast to the "columnName" and "tableName" fields, which are strings). Why is this field not considered in the calculation?

Viewing all articles
Browse latest Browse all 2993

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>