[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 knutsp):

 Replying to [comment:26 binh]:
 > I also need this. Because I work on site with thousands of products. And
 storing them togehter with post and pages, media, etc in 1 table cause it
 so hard to do bulk editing/copying/export/import.
 Any plugin can put their data in custom tables, and hundreds do, like
 WooCommerce do for many objects. The post_type column is indexed, so I
 don't see unsolvable problems with export/import/bulk actions.

 I can't see why core should support this, given the complexity with unique
 IDs that has to be solved. Each plugin will have their way of dealing with
 this, have tables with other columns and indexes. So even if core
 supported this natively, it would not be sufficient.

 Core provides database layer API for anyone to use to make special tables,
 without having to establish their own database connection.

 Custom post types can be stored in custom tables, and Pods Framework
 Advanced Content Types does this their way. So can therefore any plugin,
 or rely on their or other plugin's solutions.

 Definitely plugin territory.

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