VCS Add File Problem

[bibi]

when adding a package to vcs from the package body
the script created in the vcs only includes the package body , the option "add spec and body as a single file" is checked in vcs preferences.

when doing the same action from the package spec it ok, package spec and body are included in the script.

 

[Marco Kalter]

We'll verify this. Maybe the function is indeed restricted to the package specification.

 

[bibi]

hi

i think i found the problem.

when the option "allow editing of db objects" is checked, adding or check-in files works ok (adding spec & body together to vcs), but this doesn't gives any indication in the editor if the file is read-only or not, so when more than 1 developer is working in the same file, bad things can happen.

when option "allow editing of db objects" is not checked, we get an indication in the editor if the file is read-only (until u check out)
but than add or check-in gives different results
(sometimes only the spec is added some times only the body is added)

this is very frustrating, we realy need to use some "locking mecanishem" in order to work as a team and not override each other work, and this can be achived right now only using the vcs plugin, but it also saves not what we asked in the vcs.

 

[Marco Kalter]

The "allow editing of db objects" option should be disabled. You are working file-based to ensure a strict VCS approach. File should be made read-only in your work area by the version control system. Otherwise you can edit files that are not checked out (in PL/SQL Developer or in any other application).

 

[bibi]

i dont mind working that way
and the local file is locked by the version control system.
but the checkin and add function of the vcs plugin
works not as expected (spec and body are not in the same file)

 

[Marco Kalter]

We'll check it out (no pun intended). The check-in function will merely check-in the previously checked-out file though. It must already contain both the spec & body. This only affects the Add function.