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 sales@march-hare.com.
The way I would approach this is to script the database structure, but
not its contents. Commit this script to the repository, and update it as
the structure of the database changes. (If you were using SQL Server
2000, for example, you would have a script that dropped the old version
of the tables and created new versions, possibly surround with bcp
commands to export data out of the old structure and import data into
the new structure). Use a standard backup application to back up the
database contents.
--
Rick Genter
Sr. Software Engineer
Silverlink Communications
<mailto:rgenter at silverlink.com>
(781) 272-3080 x242
This e-mail, including attachments, may include confidential and/or
proprietary information, and may only be used by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify
the sender by replying to this message and delete this e-mail
immediately.
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Siegfried Heintze
Sent: Tuesday, October 19, 2004 1:04 AM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Synchronize source code with database?
I'm using perl and a Microsoft Access Database to implement a web site.
(Not
my choice -- but it pays the bills).
I just added some new columns to the 10MB database. Now I'm using CVSNT
to
store the perl code but not the Microsoft access database.
Should I add the Microsoft Access database to the repository? Since we
don't
have any customers yet, there is not much interesting in the database
except
the metadata. I really don't want to store a new copy of the Microsoft
Access database every time I commit. If I add the database with the -kb
option, will it store a new copy of the database every time I commit the
sandbox (assuming the database has been modified -- which is extremely
likely)?
I believe so.
This is a problem because if I ever change some field names or table
names
in the database and need to role back, I won't have an old copy of the
database to match the code!
Well, this problem is not unique to Microsoft Access. What do other
folks
do?
Thanks,
Siegfried
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs