People need to think outside their brains, and in regard to source control, I feel we need to make more packages that interface well with a good RDBMS rather than create our own RD functionality in 40ks. What's the use?
Anyone know a good system of incoroprating source control with a databases? Oracle and Postgres would do.
Katie (available here) uses postgresql to store all its metadata. Using a real database has certainly helped a lot in terms of ease of implementation (as you said, not reinventing the wheel).
I'm not saying it's a "good" (as in "usable") system yet, but it is definately getting there.
File and directory revisions, branches, labels, dynamic views, and config specs are all already implemented and working nicely. You should try it out:-).
I'm using PostgreSQL to store all the metadata, and regular files for each revision. A storage manager is in the works to allow RCS, xdelta, or whatever backend storage you want. At the file/database level, Katie is not compatible at all with ClearCASE -- it's only compatible from the user interface POV.
LAN "Remote" clients yes (I'm using NFS). Internet-remote clients no (NFS is obviously too slow). There are plans to make that work nicely, but I'm working on getting the local stuff happening first.
I didn't write the comment about 'reverse engineered bytecode'. I have no idea what the author of that comment is talking about.
I'm not sure who the "I" in the sentence "I wrote an open-source implementation" is, but it's not me (the author of Katie, the linked-to project). I have no idea as to what the author of that comment is talking about WRT "reverse engineered" and "bytecode".
All of the Katie code (with the exception of the SunRPC and Perl RPC interfaces) is my original work. It is designed so that the user interface is similar to ClearCase, but I have done no reverse-engineering apart from reading the CC docs and observing the CC user interface.
Slashdot Mirror
People need to think outside their brains, and in regard to source control, I feel we need to make more packages that interface well with a good RDBMS rather than create our own RD functionality in 40ks. What's the use?
Anyone know a good system of incoroprating source control with a databases? Oracle and Postgres would do.
Katie (available here) uses postgresql to store all its metadata. Using a real database has certainly helped a lot in terms of ease of implementation (as you said, not reinventing the wheel).
I'm not saying it's a "good" (as in "usable") system yet, but it is definately getting there.
File and directory revisions, branches, labels, dynamic views, and config specs are all already implemented and working nicely. You should try it out :-).
I'm using PostgreSQL to store all the metadata, and regular files for each revision. A storage manager is in the works to allow RCS, xdelta, or whatever backend storage you want. At the file/database level, Katie is not compatible at all with ClearCASE -- it's only compatible from the user interface POV.
LAN "Remote" clients yes (I'm using NFS). Internet-remote clients no (NFS is obviously too slow). There are plans to make that work nicely, but I'm working on getting the local stuff happening first.
I didn't write the comment about 'reverse engineered bytecode'. I have no idea what the author of that comment is talking about.
I'm not sure who the "I" in the sentence "I wrote an open-source implementation" is, but it's not me (the author of Katie, the linked-to project). I have no idea as to what the author of that comment is talking about WRT "reverse engineered" and "bytecode".
All of the Katie code (with the exception of the SunRPC and Perl RPC interfaces) is my original work. It is designed so that the user interface is similar to ClearCase, but I have done no reverse-engineering apart from reading the CC docs and observing the CC user interface.