[wp-trac] [WordPress Trac] #10483: Change post_name's length from 200 to 400

[WordPress Trac]

#10483: Change post_name's length from 200 to 400
--------------------------------------------+-----------------------------
 Reporter:  elnur                           |       Owner:  SergeyBiryukov
     Type:  enhancement                     |      Status:  reviewing
 Priority:  normal                          |   Milestone:  Future Release
Component:  Permalinks                      |     Version:
 Severity:  minor                           |  Resolution:
 Keywords:  dev-feedback needs-patch early  |     Focuses:
--------------------------------------------+-----------------------------

Comment (by dd32):

 Replying to [comment:42 netweb]:
 > I see MySQL 5.0 is now down to 2.2%
 >
 > @dd32 Hows the extended stats look that you have access to, could we
 bump this for WP 5.0?

 @netweb:
 MySQL 5.0 is at ~1.0% for WP 4.8+4.9.
 MySQL 5.1 is at ~2.5% for WP 4.8+4.9.

 In order to take baby steps forward, I've dived into the data to figure
 out what the minimum version numbers we can update to without even
 thinking twice about it.
  - 5.0.90~5.0.96 accounts for 85% of sites running MySQL 5.0.
  - 5.0.44+ is where the majority of sites are who aren't running the
 latest releases starts - That would account for 98% of the 1.0% running
 MySQL 5.0.x
  - 5.0.16+ is the next major point worth mentioning. At this point the
 percentage of sites I'm talking about is so small it's not worth
 calculating.
  - 5.0~5.0.15 is used by a handful of recent sites, but mostly WP 2.x/3.x.

 If we want to bump the MySQL version, just because we can, pick a version
 - `5.0.16` or `5.0.44` would be my suggestion - either of them would allow
 this ticket to be fixed. It just depends on what bugs/features were added
 during the MySQL 5.0 cycle.

 Bumping to `5.0.16` is a no-brainer. Bumping to `5.0.44` might affect a
 few people, but I doubt you'd hear about it. I think if we accidentally
 started using a `5.0.44` feature and didn't bump the requirements, we'd
 probably not even hear about it.

 If we want to drop support for MySQL 5.0, I'd ask for a feature that 5.1
 has that we need. There's enough sites on 5.0.90+ which makes keeping 5.0
 support worthwhile, for now.

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