VCS Check In Doesn't Save Code Changes

[Anthony Harper]

Hello Marco,
The new VCS feature enabling checkin checkout from database objects (instead of files) overcomes most of my objections to using source control in a PLSQL environment. The source control is not worth much unless it works in the background and forces the developers on the team to use it...this enhancement makes it much more dependable and simple to use. If the source control depends on developers having to check out files, save them as files and check back in, it makes Oracle PLSQL code more difficult to maintain and develop.
There is still one major problem, and I would like to submit a request that you add it as a bug fix as soon as possible. I have tested this with MS VSS and the CVS (w/ PushOK) repositories/clients. On editing a database object that has been checked into the database, the checkout happens in the background. If I make changes to several objects, compile the changes and compile the changes, then all objects I was forced to automatically check out are showing as checked out. So far so good, but if you then go to the vcs menu and bring up the check in dialog, after selecting the objects to check in and checking them in, the changes only show up in the source repository if you had the object code editing windows open at the time you check the objects back in. It looks like the checkin only updates source control properly if you have the editing window open during checkin. At least prompt when a window with an edited object that has been compiled into Oracle is being closed (ask me if I want to checkin the code at that point if the window must be open, it would be better to eliminate the need to have the edit window open)....this is a significant issue and I need it resolved to really commit my development team to using source control.
A more minor issue is that I cannot select multiple database objects at the same time and add them to source control all at once. I would classify this as a convenience enhancement...I am willing to add the items to source control one at a time.
Regards,
Anthony Harper

 

[Marco Kalter]

If you check-out database objects, then you should not check-in files. It's one or the other.

 

[Anthony Harper]

Okay, that works...and you can check in the objects from the object browser (this then opens the window in order to check in the object).
Is it possible to have a check in objects option from the VCS menu to check in a set of objects that have been checked out and modified? Or else you could only show check in objects if the preference was set to allow checkout of database objects? Also, can you show the checked out status in the object browser, something like an unlocked icon for current checkouts?

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[Anthony Harper]

Marco,
What is the status of this enhancement request? We still have a critical need for two things:

A visual indicator in the object browser that an object IS CHECKED OUT.

An option in the VCS menu (or anywhere), to VIEW/CHECK IN ALL OBJECTS THAT ARE CURRENTLY CHECKED OUT or to undo object checkouts.

Additionally, we just discovered that you can UNDO a checkout without recompiling the old version so that source control reverts but the database still has the old changes. Also, you can check in a change that has never been compiled.

Also, for initial setup of source control projects, there needs to be an option to bulk checkin database objects as a group.

These are all significant risks in the adoption of enterprise source control integrated with the developement IDE.

 

[Marco Kalter]

We had (and still have) plans to integrate the VCS Plug-In into PL/SQL Developer, so that we can create a tighter integration and provide more consistency options. At the moment the VCS Plug-In is primarily file-based, so there are no checks between database objects and controlled files.