On 12-8-2014 19:22, Dalton Calford wrote: > May I ask why you say a database system is not suitable for CVS? I had > ours on cvs for a few years before moving it to git. > > If you view the operational database as source code, then I can > understand your point, but, I view an operational database as a compiled > end product while the DDL/DML is the source code that has version > control applied to it. > > A standardised DDL/DML extraction tool is all you need. Very simple to > setup, very simple to apply the finished product to a database. > > Part of a standardised build process, of creating and populating a sand > box database via scripts, is very easy to setup. > > I am just trying to understand where you are coming from as this has > always been possible from the days of interbase.
I think you misunderstand. Historically, the error messages within the build where stored inside a Firebird database. That database itself was the source for the generated header with errorcodes and the firebird.msg file. CVS has its share of problems with storing binary files (although that isn't really relevant anymore as the project doesn't use CVS anymore for Firebird core). Second - and IMHO more important - not being able to (easily) diff or merge changes with a binary file where you can with a text file (or: sql script). Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
