[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS best practice
CVS best practice
Thu, 22 Jul 2004 11:07:24 -0700
My question is more a question of best practice as opposed to how to use
The system I work on consists of a number components. Each component is
a separately built Java application, all referencing portions of a
common database. Different components use different tables; some tables
are shared by many components, while some are used by a single
component. Over the life of the system, schema changes on the same table
may have been required by different applications for different purposes.
We script all of our database changes and store the scripts in our
repository, but this has led to some "spirited" debate about repository
structure. Our DBA wants to have a database-centric repository hierarchy
where all database scripts are stored in a CVS module named for the
database to which the script applies. There would be submodules for
Tables, Stored Procedures, Indexes, etc. I, on the other hand, want
scripts associated with a particular application to be stored in "SQL"
or "Schema" submodule under the module for that application.
What do others do?
Sr. Software Engineer
(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
- CVS best practice,
Rick Genter <=