RE: Source Control for DB objects

  • From: Jeff Chirco <JChirco@xxxxxxxxxx>
  • To: "norman.dunbar.capgemini@xxxxxxxxxxxxxxxxxxxxxxxxx" <norman.dunbar.capgemini@xxxxxxxxxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 5 Aug 2011 15:42:05 +0000

What about this scenario.
Say user A is working on a package and then user B needs to finish working on 
the package where A left off.  Is the only way user B can get user A's changes 
is if he commits/ check in his changes? But it is not in production yet so how 
can I tell what version is in production.  Currently I only have my developers 
check in their source when it has been moved to production, that way it is very 
easy for me to tell what is in production.
Thanks

Jeff | Database Administrator


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Dunbar, Norman (Capgemini)
Sent: Friday, August 05, 2011 6:52 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Source Control for DB objects

>> Norm's given a good comprehensive reply,
Ta!

>> with subversion you
>> don't take any kind of lock when you checkout. 
This is indeed the case. One of the tenets of Subversion is to completely avoid 
locking files.

>> My understanding of it is that a checkout is really just a download 
>> of a given version of the files to your machine.
Yes. When you checkout a file/folder/tree/project, you are downloading a copy 
of everything that you requested as of a particular point in time - that point 
being the most recent commit (to that project).

>> There is a separate operation to take a lock on file(s), but this is 
>> explicit.
It is explicit and I've never had to use it.

One other thing I really should mention, NEVER EVER rm a file or folder under 
version control. Use the Subversion tools to do so. Ditto for renaming a file.

You can get your working folder into all sorts of trouble if you do so plus, a 
commit or update may break.

I've had to sort out a couple that other people did when they removed a folder 
then recreated it with the same name. It is not the same *object* as the one in 
the repository. Grief all round!


Cheers,
Norm.

Norman Dunbar
Contract Senior Oracle DBA
Capgemini Database Team (EA)
Internal : 7 28 2051
External : 0113 231 2051


Information in this message may be confidential and may be legally privileged. 
If you have received this message by mistake, please notify the sender 
immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should 
still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under 
the Freedom of Information Act, Data Protection Act or for litigation.  Email 
messages and attachments sent to or from any Environment Agency address may 
also be accessed by someone other than the sender or recipient, for business 
purposes.

If we have sent you information and you wish to use it please read our terms 
and conditions which you can get by calling us on 08708 506 506.  Find out more 
about the Environment Agency at www.environment-agency.gov.uk
--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l


Other related posts: