Re: concurrent development on a database

Thank you. We're using QVCS etc., but that is not the problem. The problem is that several developers are working on the same databaseinstance,  and you always run the risk of been overwritten by another. You can make an agreement like "ask all others before start editing anything", but then you are reliant on each developer's care.

On 24 Oct 2002 11:01:36 -0500, Pablo Sanchez <pablo_at_dev.null> wrote:

>rainer.hirthammer_at_software-objects.com (Rainer Hirthammer) wrote in
>news:3db81132.26656439_at_news.btx.dtag.de:
>
>> (ORA 8.1.7) If anybody wants to edit e.g. a package we have to
>> arrange with colleagues to avoid of overwriting by another. Is it
>> possible to lock or hide packages?
>
>This appears to be more of a software development question rather
>than an Oracle question. For example, if you had a gang of
>developers developing an application in C, if one file was used,
>it'd be tenuous to merge their changes.
>
>Instead, what one does is functionally break the problem into
>separate physical files so that multiple developers can work in the
>respective areas. This methodology is glued together with a
>respectable software revision control system (such as CVS) and now
>you have source code control and concurrent development.
>
>Given the above, you can have packages that correspond to discrete
>functions within your application and use source code control to
>control the revisions.
Received on Fri Oct 25 2002 - 04:58:13 CDT