On Monday, the Subversion project is scheduled to release version 1.0 of their version control system, under development for several years now. Subversion was intended from its inception as the CVS replacement and it comes with many important features previously found only on commercial VCS like Perforce. It was designed for better remote performance, and it is multi-platform with a GUI/CLI front-end.
Permalink for comment
To read all comments associated with this story, please click here.
I don't understand one thing, why are they using a Database to store files. The best thing i like about CVS is that its repository has same hierarchy as a checked out project and it is so easy to manipulate. You can easily move files around in repository, rename them or do anything without ever worrying that you will lose versioning. Also because all repository files are stored as normal files, you can manipulate them using any existing file system tool.
Why SubVersion is using a DB to store repository? It seems stupid to me.
I don't understand one thing, why are they using a Database to store files. The best thing i like about CVS is that its repository has same hierarchy as a checked out project and it is so easy to manipulate. You can easily move files around in repository, rename them or do anything without ever worrying that you will lose versioning. Also because all repository files are stored as normal files, you can manipulate them using any existing file system tool.
Why SubVersion is using a DB to store repository? It seems stupid to me.