rob006 Since revisions are stored in separate table, which is accessed only if someone opens popup with list of posts revisions, it shouldn't matter from performance perspective.
I am with @rob006 here. Storing full revisions is far more future proof. The gain in performance* (if there is any at all) will not be worth the potential hassle. Having the revisions in a separate table is the way to go.
Kylo Imagine a board with 10k posts and all of them have 4 revisions.
This is an unrealistic assumption. From my experience, one revision for every post (on average) is already on the high side of a realistic expectation, most posts never get any edits.
jfcherng Some thoughts for storing the whole post:
- Only keep the latest N revisions in the DB
- Auto (or provide a manual way) delete outdated revisions (like 1 year ago) from DB
- Only provide revisions for the main post but not replies (like WordPress)
In my opinion none of these measures is needed, the first two wouldn't be very effective either.
Edit: * by storing only the diffs