|
Saturday 03 May 2003 3:27:02 pm
Hi,
I was asking Bard about this (removing old versions, archiving concept) some months ago.
While the database might not be a huge problem, files are.
I'm not talking about performance, but disc space.
Let's say, we have one object with a 5 MB file attached and have lots of versions of this object. The versioning system MUST keep copies of the old text/integer/whatsoever data in the DB and MUST keep copies of the old versions of the file (or image). I guess, this is working.
Now, when i've got 20 version x 5 MB x number of similar objects.... I see a need to mark old version for archiving and providing some way to archive the binaries with the data from the DB. A good versioning system must provide this.
As archiving needs a way to restore the archived data (would be more difficult than archiving, I guess), what about a "Delete" button for old versions for the beginning? Yes, _we_ have a setup like this, as we have one installation of ezP2, which has a big "document management" part in it. As ezP2 does not handle versions, we don't have this problem at the moment (we just have the current version on the web server)
Marco
http://www.hyperroad-design.com
|
