Bug #16387
closed
DBAL should honour forceCharset setting
0%
Description
DBAL (and the standard installer) should honour forceCharset setting when creating a DB and when creating tables and columns.
Many DB systems support a (default) charset/collation of a DB scheme. On some DBs you may or even must use specific column type settigns for specific charsets. eg you may set a charset for columns in Mysql but you must use NVARCHAR for Unicode data in Oracle.
(issue imported from #M3899)
Updated by Karsten Dambekalns over 17 years ago
Oracle stores data in the databases default character set, that can be some Unicode encoding eliminating the need for NVARCHAR.
As the DBAL doesn't create the database, I would leave it to the admin creating the database to set a default encoding that makes sense for the project.
Updated by Martin Kutschker over 17 years ago
It seems only Mysql supports different charset for tables and columns. I think this should habdled by the Core Mysql implementation, so I agree with the closing of this bug.