Here’s a list of changes to the wordpress schema from wordpress 2.3 to wordpress 2.5. This information will be useful for plugins and themes developers. Most of them are merely a change in the tables field’s data type anyway.
*Table: comments
Changed ‘comment_approved’ to varchar(20) NOT NULL default ‘1′
Added KEY ‘comment_approved_date_gmt’ (comment_approved, comment_date_gmt)
Added KEY ‘comment_date_gmt’ (comment_date_gmt)
*Table: links
Changed ‘link_visible’ to varchar(20) NOT NULL default ‘Y’
*Table: options
Changed ‘autoload’ to varchar(20) NOT NULL default ‘yes’
*Table: posts
Changed ‘post_status’ to varchar(20) NOT NULL default ‘publish’
Changed ‘comment_status’ to varchar(20) NOT NULL default ‘open’
Changed ‘ping_status’ to varchar(20) NOT NULL default ‘open’
*Table: term_relationships
Added ‘term_order’ int(11) NOT NULL default 0
Source: Web Blog Tools Collection
[...] probably not much people have been testing it yet. But judging by the fact that not much database schema changes for wordpress 2.3 to 2.5 has been done, I’m hopeful *most* plugins and themes should still work nicely with the new [...]
[...] added and the data length of some of the default fields were extended. You can see these changes here Share This | RSS Feeds | Email [...]
[...] and the fix may elude some users. After Googling a bit it was easy to see the issue was due to a database schema change in the wp_comments [...]