increase post_type field length from varchar(20) to varchar(100)

[ajwah]

I complained about this issue here: ​https://wordpress.org/support/topic/why-should-post-type-names-be-between-1-and-20-characters-in-length?replies=1#post-8523345

Someone provided this history:
​https://ticket2604.wordpress.com/2016/06/13/why-post-type-name-is-limited-to-20-character/

which is indicative to the fact that there should be no reason to restrict the length of post_type etc. to only 20 characters.
If you want to cut straight to the chase, then read this:
https://core.trac.wordpress.org/ticket/2604#comment:5

[dd32]

I'll copy a reply from #39507 to here for future discussion:

Worth noting that comment_type and post_type are both VARCHAR(20) while taxonomy is VARCHAR(32).

I'm not sure I see benefit in these fields being longer, they're designed as a short unique grouping of objects.

[Howdy_McGee]

Since it's been a few years since this has last been updated and the stance hasn't changed this can probably be labelled as wontfix or maybelater.

[ocean90]

#50265 was marked as a duplicate.

[ninetyninew]

Agree with the original poster on this. I've had to make an exception just for post types to my own naming conventions due to this - there are scenarios where you wish to use a unique prefix for a post type to avoid clashes but can't then give the post type a descriptive enough name due to the limit.