[wp-trac] [WordPress Trac] #19111: Post ID by Hash

[WordPress Trac]

#19111: Post ID by Hash
-------------------------+------------------------------
 Reporter:  braydonf     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Database     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+------------------------------

Comment (by braydonf):

 Replying to [comment:3 scribu]:
 > Why not just use a custom field to store a unique hash?

 1. Functions like get_post work on the ID and not on the custom fields.
 2. It would require another query to determine which hash is for what ID.
 3. Why have two IDS when there could be one?

 > Also, what's the use-case for "merging and branching" posts between
 sites?

 Use-case: There is a website at http://sample.com/ of documentary
 journalists and photographers who for most of the time are not connected
 to the Internet; at airports, buses, and traveling constantly. They have
 identical copies of the entire website stored locally so that they can
 work on preparing posts while they are offline, once they are back online
 they can quickly send their changes and add their articles and receive new
 articles and updates from others. IDs should remain the same for each
 writer because some of the posts may not be immediately published and the
 other writers can edit and add to the story before it is finally
 published. Examples could be between the writer and a photographer with
 different skills, or two people with the same skills but different
 locations and points of view.

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