[wp-trac] [WordPress Trac] #11322: Changes needed to schema for new options table keys

[WordPress Trac]

#11322: Changes needed to schema for new options table keys
--------------------------+-------------------------------------------------
 Reporter:  nacin         |       Owner:  ryan     
     Type:  defect (bug)  |      Status:  new      
 Priority:  high          |   Milestone:  2.9      
Component:  Database      |     Version:  2.9      
 Severity:  major         |    Keywords:  has-patch
--------------------------+-------------------------------------------------
 Looks like dbDelta is attempting to modify the new option_name and
 autoloaded_options keys. Not a blocker as I first thought -- dbDelta fails
 silently -- but $wp_queries is invalid in dbDelta's eyes, so it should be
 changed.

 This is due to the very finicky nature of dbDelta, in this case requiring
 the word "KEY" in addition to "UNIQUE" and not wanting spaces between
 fields in an index.

 Ideally, dbDelta can be improved in the future by preventing such
 stumbles, particularly with regard to whitespace.

 The Codex should probably be updated as well. It currently identifies the
 two spaces required for primary keys and the need to use KEY over INDEX,
 but it doesn't mention other whitespace requirements.

 Xref: #11266, #10404

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11322>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software