[wp-trac] [WordPress Trac] #14558: Separate Database Table Support for Custom Post Types

[WordPress Trac]

#14558: Separate Database Table Support for Custom Post Types
-------------------------------+----------------------
 Reporter:  rahul286           |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:  wontfix
 Keywords:                     |     Focuses:
-------------------------------+----------------------

Comment (by Mte90):

 Just to reopen the floor, this is starting to be something urgent to do.
 Now every plugin handles that in a custom way with bloating of resources,
 different standards and developers that ignore that part.
 It is easy now using some plugins that add post types likes for log,
 discussions, learning systems, revisions (that with gitenberg are vary a
 lot) and so on to get easily thousands of rows in the `wp_posts` table.
 It is quite difficult to keep the database healthy if WordPress itself
 doesn't offer an API, like did when the custom post types was created.
 Right now there are different tools that are merging (liks berlindb
 presented at WCEU 2019) and many others.
 Also as logic handle in that table different kind of post types that are
 not posts but maybe products is not so good.

 Basically there are a lot of reasons to do this:

 * Create a better database organization
 * Improve the caching
 * Teach to developers better development habits

 I don't think that we need to create a different schema but the same, only
 that use a different table for that specific post type.

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