[wp-trac] [WordPress Trac] #20564: Framework for storing revisions of Post Meta
WordPress Trac
noreply at wordpress.org
Mon Apr 1 08:22:52 UTC 2013
#20564: Framework for storing revisions of Post Meta
-------------------------------------------------+------------------
Reporter: alexkingorg | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.6
Component: Revisions | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-testing needs-codex |
-------------------------------------------------+------------------
Comment (by azaozz):
> The original post contains all those meta keys with empty values as
well...
Not sure that's needed either.
> ...the revision post is a complete copy, so I think that's the expected
behavior.
No, not a complete copy. It's a copy of the post data, most fields are not
revisioned. By default only title, content and excerpt are. That's why we
have `_wp_post_revision_fields()`.
Imagine a small site with 100 posts, each having 10 revisions. That's
(1,100 * 7) nearly 8,000 rows in the post meta table just for post
formats. And most will be empty. Now imagine a bigger site with 20,000
posts and 50 revisions each (that's not uncommon). Nearly 8,000,000 rows.
And now imagine a really big site... :)
> I also think that there should be a more general approach for all
possible meta, rather than post formats only.
Yeah, when we open the API to revision post meta (agree with @markjaquith
it's out of scope at the moment), thinking it should be opt-in. A lot of
the post meta doesn't need to be saved in revisions.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/20564#comment:46>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list