This isn’t a huge deal, but I’m wondering if this will be changed in the future.
Currently if you run a change like:
on a VARCHAR2 column in oracle the generated sql will be something like
- SQL ALTER TABLE table MODIFY (cssClasses CLOB)
which will return with a ORA-22858: invalid alteration of datatype.
To get around it I’ve just created a seperate changeset for the oracle database that creates a new column and copies the data over:
update table set tempCssClasses = cssClasses
I realize I could just create a custom change to handle this, but I’m wondering if this is a common enough problem that Liquibase might be changed in the future to handle this automatically?