CVS in collaborative environment

[Arnaud]

Hi,

I try to use CVS binding work with PL/SQL Developer 7.1.5

Environment : PL/SQL on local XP, Oracle database on remote unix server.

After searching on the forum for the best solution , I finally installed :

- the VCS plugin
- PushOK CVSSCC

I configured the stuff as described in the VCS Plugin doc, i.e. :

Tools / Preferences :

• Allow editing of database source = Disable
• Allow compilation of read-only source files = Disable
• Ask to save edited database source = Disable

VCS / Preferences :

• Allow version control over DB Objects = Enable
• Add Spec and Body

Basically it works, but when I checkout a package spec & body, make some changes and compile, the changes are visible by all people on the server.
Even if don't checkin (commit) the changes from the VCS menu.

Is it normal ? I'm afraid the answer is yes since it's the normal behaviour of PL/SQL developper with the database when not working with source control binding.

If so, using Source Control with PLSD can only achieve history log, and not collaborative / isolated development. Am I right ?

 

[Marco Kalter]

I assume you mean that the result of the compilation is immediately visible in the Oracle database for other people? This is true if they use the same Oracle user, or -more general- if they access the same package from the same owner.

To completely isolate developers from each other, you must provide them with separate users (schema's) in the the Oracle database. This way each developer has their own set of program units, tables, views, sequences, and so on.