Hi!
I am also facing effects of missing support for collation. Having a chance to define custom collation at column element would be helpful. I mean, if there can be support for encoding attribute (which apparently does nothing on MS SQL), one extra attribute for collation would surely not harm anything.
Currently when someone needs to define a custom collation, not neccessarily for the purpose of ordering but also for controlling case sensitivity or accent sensitivity (my situation), then the user is basically left in dark with poor options. If there was at least <modifySql> allowed at column level but unfortunatelly it's not.
Sure, raw <sql> works somehow but it's cumbersome and not really right tool for collation adjustment. MS SQL example:
<sql>
ALTER TABLE [table] ALTER COLUMN column1 [varchar](30) COLLATE ${collation.insensitive} NOT NULL
</sql>
See? Technically there doesn't seem a way to change collation alone without having to manipulate (redefine!) column type and constraint. I have no desire to define column type constraint twice in the changelog (once in proper table definition and second in sql). That's would be plain bad practise.
Has anyone managed to deal with collation definition in Liquibase changeset in a sensible manner? At this point I am inclined to give up, which would be a pitty.
Tomas
I am also facing effects of missing support for collation. Having a chance to define custom collation at column element would be helpful. I mean, if there can be support for encoding attribute (which apparently does nothing on MS SQL), one extra attribute for collation would surely not harm anything.
Currently when someone needs to define a custom collation, not neccessarily for the purpose of ordering but also for controlling case sensitivity or accent sensitivity (my situation), then the user is basically left in dark with poor options. If there was at least <modifySql> allowed at column level but unfortunatelly it's not.
Sure, raw <sql> works somehow but it's cumbersome and not really right tool for collation adjustment. MS SQL example:
<sql>
ALTER TABLE [table] ALTER COLUMN column1 [varchar](30) COLLATE ${collation.insensitive} NOT NULL
</sql>
See? Technically there doesn't seem a way to change collation alone without having to manipulate (redefine!) column type and constraint. I have no desire to define column type constraint twice in the changelog (once in proper table definition and second in sql). That's would be plain bad practise.
Has anyone managed to deal with collation definition in Liquibase changeset in a sensible manner? At this point I am inclined to give up, which would be a pitty.
Tomas