WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #35249, comment 21


Ignore:
Timestamp:
12/30/2015 04:27:41 PM (5 years ago)
Author:
dossy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35249, comment 21

    v1 v2  
    1818I suppose this should be filed as a new ticket, referencing this ticket for detailed background rationale, and let the community decide if they collectively think it's a good idea?
    1919
    20 I'm not keen on the idea of the installer ''changing'' the character set and collation on an ''already existing'' database that's being installed into.  `DB_CHARSET` controlling the charset/collation of a database that's being ''created'' as part of the WP installation, I'm all for.  But, if I intentionally created a database OR (regardless of whether it's a bad idea or not) want to install WP into a previously existing database, and it quietly ''changed''* the default charset/collation of the database out from underneath me?  That would be really bad, and would break assumptions made by other users of that database.
     20I'm not keen on the idea of the installer ''changing'' the character set and collation on an ''already existing'' database that's being installed into.  `DB_CHARSET` controlling the charset/collation of a database that's being ''created'' as part of the WP installation, I'm all for.  But, if I intentionally created a database OR (regardless of whether it's a bad idea or not) want to install WP into a previously existing database, and it quietly ''changed'' the default charset/collation of the database out from underneath me?  That would be really bad, and would break assumptions made by other users of that database.
    2121
    2222But, if everyone else thinks it's a good idea, I guess that's what really matters ... so, put it up to the community with a new ticket?