--- Brandon Brinkley <[EMAIL PROTECTED]> wrote: > I've worked on an Oracle Financials customization > project that sounds very > similar. No single developer owned the database, > but there were also two > additional databases for integration testing and > QA/UAT. The private > project approach was the choice of the developers > and works fine for this > type of project, but the "shared" approach would > have worked equally well.
IMHO, ideally, developers should not be sharing any resources. For example, let's say developers are sharing a database. What happens if a developer drops a table, or renames a column, or changes a stored proc? Another example, let's say developers are sharing an application server. What happens if a developer bounces or crashes the server? The worst case is when developers share source, as the original poster wanted. What happens if multiple developers vi the same file or temporily break the build in some way? Of course, the developer was asking about SQL files, but similar problems exist: What happens if a developer renames a stored proc, changes the arguments to one, or changes the type of a column? Of course, if there are only a few developers, the problems from above may be tolerable. OTOH, if there's more than just a few developers, work starts to become fighting amongst each other. >From what I've seen, resolving the issues brought about by shared resources can cost more than the disk space saved by them. Noel __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
