[wp-trac] [WordPress Trac] #9674: Better support for custom post types

[WordPress Trac]

#9674: Better support for custom post types
------------------------------------+---------------------------------------
 Reporter:  wnorris                 |        Owner:  ryan    
     Type:  task (blessed)          |       Status:  reopened
 Priority:  normal                  |    Milestone:  3.0     
Component:  Administration          |      Version:  2.9     
 Severity:  normal                  |   Resolution:          
 Keywords:  has-patch tested early  |  
------------------------------------+---------------------------------------

Comment(by Denis-de-Bernardy):

 Replying to [comment:95 filosofo]:
 > However, I wonder (since you haven't elaborated) if the issues that make
 a "dozen products, 10k users, and 15k orders" problematic wouldn't also
 afflict a blog with multiple posts, 10k users, and 15k comments (or maybe
 instead 15k comment subscriptions or something).  In other words, wouldn't
 the refactoring necessarily to make wp_posts work for generic objects also
 benefit its use for posts?  (I'm curious about your answer even though
 it's obviously beyond the scope of this ticket).

 Basically, if your goal is to merely list a few dozen restaurants in your
 community, then the posts table will work fine indeed.

 If, however, the purpose is to allow users to search for a $15-25
 restaurants in an arbitrary location, even moderate amounts of data will
 reveal that the postmeta table is not appropriate to store those details.
 (Among other things, you'll want the geodata in a column of its own right,
 complete with a GIST index.)

 I think that we should make it very clear, if we change the terminology,
 that the posts table is only appropriate for other types of data if that
 table, rather than the postmeta table, is storing the key information.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9674#comment:97>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software