[wp-trac] [WordPress Trac] #881: Lengthen password field for protected posts

[WordPress Trac]

#881: Lengthen password field for protected posts
--------------------------+-----------------------------
 Reporter:  ScytheBlade1  |       Owner:  pento
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:  Future Release
Component:  Database      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------

Comment (by pento):

 Replying to [comment:26 adamsilverstein]:
 > I like the suggestion of just lengthening the database field. I know
 these types of database schema changes are rare, however we do make them.
 @pento you said "This won't be a fun thing to roll out." - can we still
 roll it out some day soon? Would you really like to see a paginated update
 routine to have this fly? What have we done with other db schema changes
 in the past?

 In the past, we've just done the schema change during upgrade. The
 `utf8mb4` upgrade, for example, turned into a bit of a shambles - sites
 regularly having upgrade problems because their connection timed out while
 the schema changes were still occurring.

 Given that experience, I'm inclined to call my figures a severe
 underestimation - they were done on a server with no load, any extra load
 will cause more downtime while MySQL tries to gain the necessary locks.

 Now, it's not possible to avoid that downtime (unless you're using MySQL
 5.6, which would allow this ALTER TABLE as an
 [https://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-overview.html
 online DDL]), but I think it's necessary for us to provide a much better
 UI for these long running schema changes (and better feedback in the event
 of something going wrong) before we can look at making another change.

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