Re: AW: Multiple cvs users in one checkout area

[Jenn Vesperman]

On Mon, 2002-10-21 at 17:05, Andreas Otte wrote:
> > Von: Mr. Cristian Romanescu [mailto:address@hidden

> > Why doesn't each user checkout his own version of the project 
> > and works 
> > on it and then commits changes?
> > Why must you have one checkout area? This is the role of cvs so that 
> > each user to retrieve a version to work on it....
> 
> The sources are sources for database objects (stored procedures, triggers, 
> ...) which are applied against a database, no user has it's own database, so 
> it makes no sense to work in different areas, everbody will see everybody 
> else's changes in the database anyway. The private sandbox isn't there. 

When I've done this sort of work (Java client accessing an oracle
database), we each had our own sandbox for the source, which accessed
shared Java oracle libraries.
So we used one database, out of different sandboxes, and compiled
against a shared set of database access libraries.

Perhaps you could do something like that? 

You can make symbolic links in your build script, if necessary, or find
some other way to use the shared resource when testing, but the
individual sandboxes/working copies, for development.


Jenn V.
-- 
    "Do you ever wonder if there's a whole section of geek culture 
                you miss out on by being a geek?" - Dancer.

address@hidden     http://anthill.echidna.id.au/~jenn/