Post ID by Hash
|Reported by:||braydonf||Owned by:|
Post IDs are currently stored as incrementing values. In the case with merging posts from two separate WordPress databases it introduces the problem of ID collisions. The step to merge posts becomes a process of importing with new IDs and breaks continuity since there would be an issue with maintaining the original ID, and able to sync back.
I'm suggesting using hashed IDs instead of incremented ID values, similar to how version control systems are currently designed.
GUID values are useful for site to site reference, however doesn't take into consideration having multiple and simultaneous systems that are able to be easily merged and branched, just like distributed version control.
Change History (11)
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed