runAlways change set that is already run and has onSqlOutput="FAIL" onFail="CONTINUE" lands in sql ouput

Description

I have a runAlways change set with a custom change that needs the previous statements to be in the real database, so I added <preConditions onSqlOutput="FAIL" onFail="CONTINUE"/> to the change set. This works fine thus far, except in case you ahve a runAlways change set that is already run and thus in DATABASECHANGELOG. In this case the resulting SQL statements include the update for DATABASECHANGELOG that pretends the change set was reran, which is plainly wrong.

Environment

.

Activity

Show:
Björn Kautler
created the IssueSeptember 24, 2014 at 2:59 PM

Details

Reporter

Affects versions

Priority

Created September 24, 2014 at 2:59 PM
Updated September 24, 2014 at 2:59 PM

Flag notifications