[wp-trac] [WordPress Trac] #14513: Time for a wp_post_relationships table?

[WordPress Trac]

#14513: Time for a wp_post_relationships table?
-----------------------------+----------------------------------------------
 Reporter:  mikeschinkel     |        Owner:                
     Type:  feature request  |       Status:  reopened      
 Priority:  normal           |    Milestone:  Future Release
Component:  Post Types       |      Version:  3.0.1         
 Severity:  normal           |   Resolution:                
 Keywords:                   |  
-----------------------------+----------------------------------------------

Comment(by nacin):

 This ticket is not going to get anywhere if it's just a lot of back and
 forth, some of it not in the most appropriate tone, complete with
 questioning the intelligence of a core developer willing to share the
 current collective opinion of the core team on this. It's only going to
 cause the folks who you want to pay attention to this ticket to simply
 mute it.

 I spent some time yesterday reading through old threads and tickets around
 the time the taxonomy schema was originally implemented in 2.2. wp-hackers
 was very effectively used as a discussion of use cases, demand, consensus-
 building on a schema and API, and the consideration of future situations.
 Tickets, on the other hand, are for code. In my opinion, a ticket like
 this -- a major feature request that can only get into core as a blessed
 task -- should not be created until it has been slated for a milestone at
 a scope meeting.

 At the moment, this reads more like a wp-hackers discussion, and it
 belongs there. If any movement is going to happen on this, there needs to
 be solid consensus on a flexible system that can address clear, popular
 use cases. I see all sorts of use cases but I'm not convinced they can't
 be implemented with the existing schema; I've also seen, what, three or
 four conflicting ideas for how this should be implemented, to the point
 where the definitions of "this" are different depending on the developer
 and the use cases they were considering.

 We need to see both demand and innovation, and preferably some consensus,
 before even considering this. Give it a year, I imagine that will evolve,
 but being ahead of one's time is not always a good thing.

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