[wp-trac] [WordPress Trac] #44814: User table same schema, single and multisite

[WordPress Trac]

#44814: User table same schema, single and multisite
--------------------------------------+-----------------------------
 Reporter:  spacedmonkey              |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Future Release
Component:  Networks and Sites        |     Version:  3.3
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback needs-patch  |     Focuses:  multisite
--------------------------------------+-----------------------------

Comment (by johnjamesjacoby):

 #34316.

 Early on (2006ish?) it was decided that maintaining the users database
 schema across all projects (GlotPress, bbPress, BackPress, WordPress) was
 more important than hunting down performance improvements to it.

 As a result, it was easier to add these new columns for multisite, to
 avoid changing user_status to a string like post_status across all
 projects.

 Today, I think that old thinking no longer applies, but the next reason
 not to change these is because index updates to large users tables will
 take minutes-to-hours to finish. WordPress.com likely wouldn’t even run
 the update, since it would require pausing sign-ups.

 Related: The last time I broke WordPress.org, it was due to a users table
 change from multisite to single site (and a missing
 DO_NOT_UPGRADE_GLOBAL_TABLES check), and it locked everything for around
 12 minutes.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44814#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform