Backup versions of content when creating an article, how to implement? (PHP, MySql)?

targz + cron

Socor is a feature of the system and not PHP+MySQL (though I think it screwed you.)
My website will very + base:
\r
1. tar-cvzf /_mybackups/NAME_www.tgz /home/NAME/public_html /home/NAME/includes — those directories which I need to turn off in the files
\r
2. mysqldump -h localhost -u LOGIN: PASSWORD -d DATABASE > /_mybackups/db_service.sql — remove the dump from the base
\r
3. tar-cvzf /_mybackups/db_service.tgz /_mybackups/db_service.the sql database archive
\r
4. rm /_mybackups/db_service.sql. dump
\r
Thus at the output of the archive database and website
\r
about the crown (Cron) Google — there is nothing complicated. And this is my Kron 4 jobs that you yourself would put what you need frequency. if necessary, you can do versioning by date. to programmirovat don't need anything — just set it and you always have archive that

Most likely there is the structure of the database enables this behavior: when you save the data not update in database are replaced and a new row is added.
\r
The simplest structure with minimal number of required fields looks like this:
— article_id (non-unique)
timestamp
— content
\r
Accordingly when you save the add a new row with the same ID, but more fresh timestampa. During selection — take the most recent (queries with grouping, any additional field being updated with a flag to pefomance).

And somehow, I'm sure that there are simply saved diffs are.
So take wordpress and see how they are stored.

Keep the article in Subversion