Thomas Svensen
Member²
A have quite successfully managed to integrate PL/SQL Dev with CVS using the SCC proxy from pushok.com (which is highly recommended, by the way).
Now, there are two problems I encounter:
1. Using version control for files, the VCS project seems to "forget" the project files every time I close a project. The (ugly) workaround is to (re-)add the files to version control every time. Add then fails, since the file is already under version control, but check-in/check-out works after that.
Should be easily reproducible, given an existing CVS repository.
2. Version control for data objects. Now that is a REALLY cool idea.
Alas, I cannot use it for two small reasons. The first: I need to do a lower-case on the package names before mapping to file name, e.g. DUAL_PKG would be stored in dual_pkg.spc. The second: I would very much like to store the files in sub-directories based on schema name.
Is there any hope that these (small?) enhancements could be added to VCS?
Have a nice day!
PS! The eternal question: when is 6.0 coming
- Thomas
Now, there are two problems I encounter:
1. Using version control for files, the VCS project seems to "forget" the project files every time I close a project. The (ugly) workaround is to (re-)add the files to version control every time. Add then fails, since the file is already under version control, but check-in/check-out works after that.
Should be easily reproducible, given an existing CVS repository.
2. Version control for data objects. Now that is a REALLY cool idea.

Is there any hope that these (small?) enhancements could be added to VCS?
Have a nice day!
PS! The eternal question: when is 6.0 coming

- Thomas