Sam Ghods wrote:
> The database may actually grow to several million rows. Also, doesn't dump include all the data?
Of course the dump contains all the data. Try the mysqldump command and look at its output. Read also the mysqldump man page; you might find some options useful.
> I wouldn't be able to revert back to a previous dump without losing data entered since that dump,
> right?
I'm not sure to understand what you mean here, and what you want exactly. IMHO, reverting to a previous state means obviously getting back to that state, so losing all stuff made since.
But the mysqldump output is textual, and you might use small textual tools to get the best of it, or even to process diffs, etc...
Otherwise, you might add a TIMESTAMP column, and (independently of any VC system like Subversion or CVS) issue appropriate MySQL queries to fetch/remove data inserted in a given period of time.
I am a bit confused by what you want exactly.
However, backing up your data thru mysqldump is always a good thing to do.
Regards.
--
Basile STARYNKEVITCH ::::
http://starynkevitch.net/Basile/