WordPress 2.3.x to 2.5 Database Schema Change

Earlier, when I upgraded to WordPress 2.5 from existing 2.3.3 setup, I had noticed the upgrade procedure, updated database. I  had then looked into, what changes has been made to the WordPress 2.5 database, and came across MichaelH post: Changes to database schema from Version 2.3 to 2.5. Table: comments Changed ‘comment_approved’ to varchar(20) NOT […]

Earlier, when I upgraded to WordPress 2.5 from existing 2.3.3 setup, I had noticed the upgrade procedure, updated database. I  had then looked into, what changes has been made to the WordPress 2.5 database, and came across MichaelH post:

Changes to database schema from Version 2.3 to 2.5.

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

WordPress, Database, Table, Schema, MySQL