[wp-trac] Re: [WordPress Trac] #8915: Multi-Byte characters not readable because "latin1_swedish_ci" is set by default of WP 2.7 Install

[WordPress Trac]

#8915: Multi-Byte characters not readable because "latin1_swedish_ci" is set by
default of WP 2.7 Install
--------------------------+-------------------------------------------------
 Reporter:  misty9        |        Owner:  anonymous
     Type:  defect (bug)  |       Status:  new      
 Priority:  high          |    Milestone:  2.8      
Component:  General       |      Version:  2.7      
 Severity:  major         |   Resolution:           
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by DD32):

 > Not true. Tables wp_terms, wp_term_relationships and wp_taxonomy are
 with "utf8_general_ci".

 When the other tables were created, WP didnt set the type, Therefor, it
 used the default mysql type, which for many, was latin1_swedish_ci

 In 2.3/2.5 somewhere there, the new taxonomy tables were introduced, when
 they got created, it used the default of utf8_general_ci instead of
 relying on MySQL to be set up well

 Now as to why the multi-byte characters broke, Would once again, Be due to
 later WP's using utf8 instead of non-utf8 types, The end result is that
 certain setups break and you need to fix them manually, simply because
 automatically converting them would be horrendously error-prone.. The odd
 thing about this is, That you should've had problems in 2.2 with this..
 which means the characters were probably being stored incorrectly in the
 first place.. See
 http://codex.wordpress.org/Converting_Database_Character_Sets for more
 info.

 As for the page counter, Thats correct. The ID's are used by posts, pages,
 revisions, and attachments, so you'll never get 1, 2, 3, 4....10000 unless
 you only create pages and disable revisions.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/8915#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software