implement `FluidColumnOptions::uniqueIndex()` ?

[dsavina]

Working on MySQL, when I use the unique() method, I get constant diff with my versioned schema, as this method only adds an option on the column, whereas an index is created when actually creating the schema in database. Therefore, I'm wondering whether it would be relevant to have a uniqueIndex() method relying on Doctrine method Table::createUniqueIndex().

If agreed, I will gladly implement it.

[moufmouf]

I'm not sure I understand. Whet would be the difference between unique() and uniqueIndex()?

Wouldn't it be better to rewrite the unique() method to use Table::createUniqueIndex() behind the scenes?

[dsavina]

My guess is that the handling for the custom option "unique" on a column as an index is a specificity of MySQL, but I might be wrong here. I'm all in for rewriting the method to use Table::createUniqueIndex() instead, though we might need to make sure that it does not break compatibility for migrations already using this unique method in existing projects.

[moufmouf]

I'd say that if a migration has already been applied in production, the change won't impact it. So... yeah.... let's make the change directly in the unique() method!