[wp-trac] [WordPress Trac] #18800: Recycle auto-draft post entries
WordPress Trac
wp-trac at lists.automattic.com
Thu Sep 29 21:07:38 UTC 2011
#18800: Recycle auto-draft post entries
-------------------------------------+----------------------
Reporter: MattyRob | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: General | Version: 3.2.1
Severity: normal | Resolution: invalid
Keywords: has-patch needs-testing |
-------------------------------------+----------------------
Changes (by markjaquith):
* status: new => closed
* resolution: => invalid
* milestone: Awaiting Review =>
Comment:
MattyRob — the issue you originally reported is invalid — it's not true.
Auto-drafts are used if you then go on to populate that post item. The
only ones that are "wasted" are the ones that, after 7 days, have not been
populated with data.
The issue with any sort of recycling is that you can't guarantee a lock.
Who gets to recycle it? What if two requests try to recycle the same item?
We have enough race conditions in WordPress. I'm not eager to introduce
another.
Your objection seems to be an aesthetic objection to something that is
fairly well abstracted. The rows are cleaned up, on a rolling basis. This
is invisible to the user. Our audience is users, not people who peer at
the database directly. The only lasting remnant is the incrementing of the
post ID. We're still a ways off from risking hitting that limit of
2,147,483,647. I still haven't even hit 6 digits on my blog. Barely have
hit 5.
Switching to this system solved a bunch of bugs, simplified our code, and
has guaranteed that we'll never see a post-creation race condition. That's
a real savings in terms of effort and frustration reduction. It'd take
more than an aesthetic objection for us to consider compromising those
gains.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/18800#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list