Failure to write a change set to the DATABASECHANGELOG table still applies the change set

Description

Running the change set below results in an error when writing to the DATABASECHANGELOG table. However the change set still gets applied, but with no trace of it ever being applied (causing future upgrade scripts to fail, because this change was never persisted in the DATABASECHANGELOG table, but the actual table was created in the database.

<changeSet author="me" id="looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooongID">
<createTable schemaName="dbo" tableName="foo">
<column name="bar" type="int">
</column>
</createTable>
</changeSet>

Is this a bug or is it me not properly using rollback elements or something along those lines?

Environment

Windows Vista, Windows XP, MSSQL

Reporter

Mikael Wahlb├Ąck

Fix versions

Affects versions

Priority

Major
Configure