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

[Karsten Dambekalns]

Hi.

On 18.03.2013, at 20:37, Rens Admiraal <renst3 at rensnel.nl> wrote:
> 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.

More precise: created with a different collation default (depending on database [server] settings).

One way would be to add charset and collation to all existing migrations for 2.0, that way everyone starting a fresh project is done with the topic. Everyone having a database with the "correct" database settings (like me, never noticed that problem) is safe then as well.

Those having a different collation in their database would need to remove the collation from migrations in the future. So, another way would be to remove collation information from all generated migrations. But there was a reason for the Doctrine guys to no longer rely on people setting good defaults.

A mix would be to give more detailed instructions on setting up the database (instead of just saying "use utf-8").

Regards,
Karsten
-- 
Karsten Dambekalns
TYPO3 Core Developer, Neos / Flow Team

TYPO3 .... inspiring people to share!
Get involved: typo3.org