Please add easy settable __COLLATION__ support to EF6 Code-First database creation and recreation (like “French_100_CI_AI”, “Cyrillic_General_CI_AI”, “Polish_100_CI_AI” etc. It is very important for __VARCHAR__, CHAR and so on database types. Also easy way to modify other default SQL Options is very important, like database __Filegroups__, __Initial Size__, __Autogrowth__, and others - long time available in MS SQL Server Management Studio during manual “New Database…” creation.
Comments: The best way to do this currently is using a SQL(string) call in a migration: ``` SQL("ALTER DATABASE MyDatabase COLLATE French_100_CI_AI"); ``` Collation isn't just a SQL Server concept and is present in most database (Oracle, MySQL, SQLite, ...) so it does make sense to have a higher level way to set this. Perhaps just as a Migrations operation that you can add to your migrations - or it could be a setting in Migrations Configuration that we use when creating databases. Taking into account where we are in the EF6 release our team is not planning to implement it in EF6. Therefore, we are moving it to the Future release to reconsider in the next release. I've marked the issue 'UpForGrabs' as someone from outside the EF team may like to consider contributing this feature into the EF6 release.
Comments: The best way to do this currently is using a SQL(string) call in a migration: ``` SQL("ALTER DATABASE MyDatabase COLLATE French_100_CI_AI"); ``` Collation isn't just a SQL Server concept and is present in most database (Oracle, MySQL, SQLite, ...) so it does make sense to have a higher level way to set this. Perhaps just as a Migrations operation that you can add to your migrations - or it could be a setting in Migrations Configuration that we use when creating databases. Taking into account where we are in the EF6 release our team is not planning to implement it in EF6. Therefore, we are moving it to the Future release to reconsider in the next release. I've marked the issue 'UpForGrabs' as someone from outside the EF team may like to consider contributing this feature into the EF6 release.