Version Control Interface - CVS integration

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 :rolleyes:

- Thomas
 
Can you try the current 1.2 version of the VCS Plug-In? It may fix problem 1, and adds the functionality mentioned under 2 ("Allow version control of DB Objects" preference).

PL/SQL Developer 6.0 is scheduled for the end of this quarter.
 
Hello,

I must say that I still do not understand people who feel need to complicate theirs life and need to use versioning system like cvs or a newer one svn within a PL/SQL Developer + vcs plug-in. Using cvs you always work on your local copy of files. So you could work on files as usual and when you finish you can update and commit. All changes will be merged into new revision. However I understand that people who use Microsoft or Microsoft compatible systems are lost and it is the only way to do it ;) .

Joachim Rupik
 
I forgot to say in my original post, I am already using version 1.2 of the VCS plug-in...

As to Rupik's reply, I am very curious about what you mean I am complicating. My goal is really to simplify as much as possible. Currently I am doing CVS via WinCVS on local copy of files, as you describe. I just thought that it would be simpler to do the whole check-in/check-out from within PL/SQL Developer, that's all...

My "dream" would be a VCS plugin with native support for CVS, of course :) That's what I have in the java world, using Intellij IDEA.

- Thomas S.
 
Thomas, what I mean is that using cvs (or svn) you do not need to lock anything on server and you have not to hurry because another programmer is waiting for you.
The philosophy is quite different. You and all your team can do the work together and simultaneously without any locking problem. When each of you finishes then do a commit. No problems no complications.
It is even simpler to use a TortoiseCVS or TortoiseSVN Windows shell add-ons. It shows you the status of your project files from shell level.
Remember VCS plugin supports SCC interface - check-in check-out (lock-download-work-upload-unlock) philosophy. CVS do not use locks at all, you do not need to look up on server to know what project files are
 
Joachim, first of all, thank you for your reply.

Regarding file locking: yes, CVS is definitely superior and I am not concerned about holding locks.

TortoiseCVS: Yes, I actually used it for more than a year, but I never really liked it. No support for "history" and sluggish performance in all explorer windows...

I actually think that the VCS-plugin + the CVS-CSS proxy is a useful solution. Even with it's current shortcomings, I think that it is the simplest way. (but of course, that's just me ;) )

- Thomas
 
Thomas, I am having the SAME exact issue as you:

" 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."

This is really a show stopper for us to use the integrated VCS functionality. Has there been an update on this?

One other symptom we see is the "Get Files dialog" does not reflect what is in the repository after PLSQL dev is restarted. Here is a snippet from my vcsdebug.log when I try to refresh the Get Files dialog:

9/17/2004 10:51:43 AM GetDirectories
9/17/2004 10:51:43 AM GetDirectories: 1
9/17/2004 10:51:47 AM OpenProject SCCProvider.Initialized
9/17/2004 10:51:47 AM OpenProject: ,
9/17/2004 10:51:47 AM Username : joes
9/17/2004 10:51:47 AM ProjectName : sql
9/17/2004 10:51:47 AM LocalPath : C:\dev\cvsrepo\HEAD\sql\
9/17/2004 10:51:47 AM LocalPath : C:\dev\cvsrepo\HEAD\sql\
9/17/2004 10:51:47 AM SCCProvider.GetFileList
9/17/2004 10:51:47 AM PopulateList
9/17/2004 10:51:49 AM PopListProc: C:\dev\cvsrepo\HEAD\sql\
9/17/2004 10:51:49 AM GetDirectories
9/17/2004 10:51:49 AM GetDirectories: 1
 
Not that you should have to buy new software to do this, but have you checked out ComponentSoftware's CS-RCS/CS-CVS product line as an interface to CVS repositories?

I've been looking closely at CS-RCS for handling our VCS needs (since we don't use CVS) and am VERY impressed for the price. Price starts at $200 per seat then drops to $140 for 5 seats, and further from there.

I love the Windows Explorer integration (though it isn't as fancy as TortoiseSVN/Subversion). I've also integrated it into our favorite text editor (UltraEdit) and PL/SQL Developer. The PL/SQL Developer works great, w/o losing track of the project.

One advantage of CS-RCS over Subversion is that it's been in production for 7 years, so not many bugs to shake out any more.

Best of luck,

Stew
 
I've been looking at Component as well, but never got it to work properly with PL/SQL Developer. Can you share your installation procedure to make the connection work?

Thanks.
 
Arnoud,

I thought it was pretty easy, though it did take me 2 tries.

As I remember, the only things I had to do were:

  • Create a new project for my Oracle objects
  • Create a new working directory for them.
  • Go to Tools->Configure Plug-ins
  • Open the settings window for Version Control Manager 1.2
  • Select ComponentSoftware RCS from the SCC list.
  • Select the project from list
  • Set the working directory

I was surprised how fast it is, much faster than StarTeam (which we previously used).

Good luck,

Stew
 
I could have sworn I tried that, but it didn;t work for some reason. It has been a while, so I'll try again...
 
Back
Top