[TYPO3-team-core-v5] Database collation in Doctrine migrations

[Christopher Hlubek]

Hi,

I think we talked about having a new feature of 0-Migrations that are a snapshot of the structure at a certain time. Maybe that could help to find a solution.

The main problem is, that a project that is in production and was built without collation (and uses some random default from the database) shouldn't be forced to use the collations by us. We all know that the update procedure with foreign key constraints is really troublesome.

Maybe a feature switch to enable the collations inside the DDL statements could help?

Greetings,

Christopher

Am 18.03.2013 um 20:37 schrieb Rens Admiraal <renst3 at rensnel.nl>:

> Hey guys...
> 
> Doctrine is now adding the collation to migrations for a while. This causes some issues if you make relations to tables created with migrations that don't have the collation set. I always just remove the collation during the check of the migrations I generate, but is that really the way to go?
> 
> Also some people run into issues with it as it seems (it pops up on ml / irc from time to time). Do we have to do something with this (maybe in changing the migrations automatically or write some docs about this?)
> 
> I'm not really sure about the complications, but I'm sure we can fiddle out the possibilities and make a nice solution ;-)
> 
> 
> Greetz,
> Rens
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5