I created a changelog file containing a changeset that inserts a record into a table with custom values passed in on the command line. For instance, I'd pass a parameter to execute liquibase from the command by specifying the custom parameter by including "-Dparam=value". What I've confirmed is that the checksum performed on the changeset varies depending on the value of the parameter. I attempted to change the column definition to use the valueComputed attribute since it seems to handle this situation (i.e. date functions obviously generate different values on subsequent executions) but that did not work.
Am I missing something/doing something wrong, or is this a defect?
Sample of insert from changeset:
<insert tableName="TABLE_ONE">
...
<column name="TEST" value="${param}" />
...
</insert>