Am 21.05.2014 00:48, schrieb Larry Martell: >> ok, in this case the interesting piece of information >> would be the "SHOW CREATE TABLE pnlCurrency;" output >> from both. >> >> As the collation_database variables differ between the >> two servers ("utf8_bin" vs. "latin1_swedish_ci") I assume >> that the same is the case for the actual tables, and that >> would perfectly explain why one treads lower/upper case >> as distinct while the other doesn't > > The create table on 5.5 has: > > DEFAULT CHARSET=uft8 > COLLATE=uft8_bin > > and on the 5.0 server it has: > > DEFAULT CHARSET=latin1 > > But the tables on both servers were created from DDL files that do not > specify either one of these. So are these inherited from the server > settings at the time the tables are created? how do I fix this?
they are inherited from the *database* get phpMyAdmin, you can learn a lot of it outputs and the generated queries of most actions > Specify DEFAULT CHARSET and COLLATE on the CREATE TABLE statements in > the DDL file and drop and recreate all the tables? Is there a way fo > change this without doing that? Can the collation_database variables > be set in the conf file? I didn't see them mentioned in the docs DDL files which don't specify charset / collation are broken because whoever writes them has no idea of the default settings surely: http://dev.mysql.com/doc/refman/5.0/en/alter-table.html ALTER TABLE `my_table` DEFAULT CHARACTER SET latin1 COLLATE latin1_general_ci;
signature.asc
Description: OpenPGP digital signature