Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Lucia.Kaeser wrote: > We maintain a large binary file (a database file) within CVS with a size > of approx. 50 MB and the module in CVS has reached now the size of > approx. 500MB. Since CVS stores all the revisions in one single file we > fear, that we once could reach the maximum size of a file and that CVS > could not store the new revision. Do you have any experience with that > large files ? Is it recommended to start e.g. with a new module for that > database each year? It is recommended not to store binary files for exactly this reason. You can try exporting the data and schema into some text format and then storing that in CVS instead. The only time you typically want to store binary files in a repository is when you have subsidiary library files which are required for building your application. And even then, you don't would only store the occasional updates as part of a specific release tag. Alternatively, you can just rename the database with a new name every month and store that in the file system. CVS is not an efficient way to back up databases files. HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747