Liquibase puts the comments on the tables instead of on the fields

[php-coder]

In the commit 89ba68c (#1326) I used setColumnRemarks:

<setColumnRemarks
	tableName="collections_series"
	columnName="cond"
	remarks="Example: MNH, CANCELLED" />

but after deploy, I see that it put it to the table instead of the field:

mysql> show create table collections_series;
...
| collections_series | CREATE TABLE `collections_series` (
...
  `cond` varchar(9) DEFAULT NULL,
  PRIMARY KEY (`id`),
...
) ENGINE=InnoDB AUTO_INCREMENT=91 DEFAULT CHARSET=utf8 COMMENT='Example: MNH, CANCELLED' |

Here is also related logs:

liquibase.executor.jvm.JdbcExecutor      : ALTER TABLE mystamps.collections_series COMMENT = 'Example: MNH, CANCELLED'
liquibase.changelog.ChangeSet            : Remarks set on collections_series.cond

[php-coder]

It seems like this is our case: liquibase/liquibase#942

[php-coder]

This bug has been fixed in 4.3.0 version and in #1526 Liquibase has been updated to 4.5.0 so now we only need to fix the data in production.

[php-coder]

Perhaps, we can play with runOnChange (https://docs.liquibase.com/concepts/changelogs/attributes/runonchange.html) to re-apply comments to a column.

[php-coder]

Perhaps, we can play with runOnChange

It doesn't work because migration also tries to rename a column again:

MySQLSyntaxErrorException: Unknown column 'condition' in 'collections_series'

[php-coder]

https://docs.liquibase.com/change-types/set-table-remarks.html can be used to drop existing comment on a table.

[php-coder]

The build is failing now (https://app.travis-ci.com/github/php-coder/mystamps/jobs/582181150):

ChangeLogParseException: liquibase.exception.SetupException: liquibase.exception.SetupException: Error parsing line 9 column 44 of liquibase/version/0.4.7/2022-09-08--re_apply_column_comments.xml: The string "--" is not permitted within comments