- January 1, 2012
- 588
- 216
- Home Country
-
Germany
Hi,
first, let me say, I am just an experienced user but not a pprogrammer in any way, so I don't know if my suggestion is a good idea or not.
I have been using MePo for a good while now and I like it very much, especially it's expandability and customizability. But it has happened to me several times now that unexpected errors occured - the most severe due to corruption of any of the databases. So my idea was to add a kind of database security by adding a backup of all database files which should be updated after either a) after a verified successful modification or b) after a specified time period.
a) Would be nice, but hard to achieve, as every addon author would need to use these routines,
b) could make backups on every startup of MePo into a subfolder (add date/timestamp to filename) and you could set in config e.g. "max 20 copies" or "max x mb disk space" before the old entries become deleted.
So, if a database gets corrupted, you could simply go back to an older, hopefully not yet corrupted version.
I have saved myself from reinstalling or at least rebuildiung databases several times by my daily incremental backups, but I suppose not everyone does these.
first, let me say, I am just an experienced user but not a pprogrammer in any way, so I don't know if my suggestion is a good idea or not.
I have been using MePo for a good while now and I like it very much, especially it's expandability and customizability. But it has happened to me several times now that unexpected errors occured - the most severe due to corruption of any of the databases. So my idea was to add a kind of database security by adding a backup of all database files which should be updated after either a) after a verified successful modification or b) after a specified time period.
a) Would be nice, but hard to achieve, as every addon author would need to use these routines,
b) could make backups on every startup of MePo into a subfolder (add date/timestamp to filename) and you could set in config e.g. "max 20 copies" or "max x mb disk space" before the old entries become deleted.
So, if a database gets corrupted, you could simply go back to an older, hopefully not yet corrupted version.
I have saved myself from reinstalling or at least rebuildiung databases several times by my daily incremental backups, but I suppose not everyone does these.