Fixed MigrationManager to use queries and charset settings

[rozwell]

Before this PR more advanced migrations might fail or cause data issues when specific database configuration was used.
Mainly custom charset or collation.

See: propelorm/sfPropelORMPlugin#204

[willdurand]

Wow, can't really say anything on this.. @propelorm who uses migrations to confirm the fix?

[rozwell]

I do ;)
We encountered encoding issues during more advanced migrations and it turns out that Propel::initConnection() executes queries like SET NAMES utf8 or adds charset parameter to the dsn (etc) - raw new PDO() does not.

[havvg]

Looks good to me.

Used a lot migrations, but never run into the issue, probably because we set everything to UTF-8 on server configuration.

[rozwell]

@havvg we're using UTF-8 too but with utf8_polish_ci collation. AFAIR without SET NAMES UTF-8 queries didn't work correctly.

[staabm]

@rozwell you need the SET NAMES statement only when the server itself does not default to a UTF-8 charset, see e.g. http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#sysvar_character_set_server

(and it is not overwritten by a database/table/connnection collation)

[rozwell]

I'm aware of that. But that's theory. I'm always using utf8 and somehow It didn't work correctly. Maybe because of collation, doesn't matter - I've got this working. Just wanted to share the fix with others :)

[willdurand]

thanks!

[willdurand]

@rozwell could you port this into Propel2?