posted on Mar, 2 2010 @ 02:39 AM
Well, pay attention to your posts, proofreading several times before clicking submit. Or... if you edit your post, insert the edit inline with the
original text altered to show the text has been superceded?
Anyhow, it's highly unlikely that old post text would be deliberately saved. The processing impact to the database to recall the original text then
apply any successive edits, or compare multiple versions of posts and retrieve the most recent one, would likely be too high to be efficiently
implemented without significant impact to page rendering. That does not mean though, that the database doesn't perform intermittent backups and could
backup a post before an edit is applied. Things like that do happen and typically show up when a site crashes and subsequently has to restore from a
backup and posts are missing and edits don't show. However, an appropriately configured database can "replay" all the edits and bring the backup to
"current" status. Also, "mirrored" databases generally do not suffer from that problem since a crash on one database server can be restored from
the more current database on a mirror.
But I've digressed.