Team,
I was interested in how most teams handle schema changes which are really fixes for earlier changesets e.g. updating the correct field value which is changed a few times within a release i.e. before any customer would ever test. e.g. consider
1) UPDATE CONFIGPARAMS SET VALUE='MYVALUE1'
2) UPDATE CONFIGPARAMS SET VALUE='MYVALUE2
3) UPDATE CONFIGPARAMS SET VALUE='MYVALUE3''
Suppose by changeset 3 this was the GA candidate. When we generated our SQL to deploy to the customer we wouldn't really want three update statements when only the last was intended.
This page provides some options
However the most appropriate solution I can see this page lists is
"In this case, it is best to use add a
<validCheckSum> tag to the changeSet specifying that the new check sum is correct"Although in other documentation references it indicates this isn't a best practise i.e.
| validCheckSum | List checksums which are considered valid for this changeSet, regardless of what is stored in the database. Used primarily when you need to change a changeSet and don't want errors thrown on databases on which it has already run (not a recommended procedure). Since 1.7 |
What is cleanest way to handle this here? What are others currently doing?
Many thanks
Matt