Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Version control of Oracle Stored Objects.

Re: Version control of Oracle Stored Objects.

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Sun, 06 Mar 2005 09:17:51 -0800
Message-ID: <1110129283.208938@yasure>


Jim Smith wrote:
> In message <1110077619.499872_at_yasure>, DA Morgan
> <damorgan_at_x.washington.edu> writes
>

>> IANAL_VISTA wrote:
>>
>>> DA Morgan <damorgan_at_x.washington.edu> wrote in 
>>> news:1110065133.857196_at_yasure:
>>>
>>>> The real BDFH builds a DDL trigger that raises an exception with all 
>>>> DDL
>>>> on the database and another that audits it. He/she then disables the
>>>> first trigger whenever making changes leaving the second one to create
>>>> the audit trail.
>>>
>>>   Alternatively, just nightly extract the current production code 
>>> from the  repository and install it into the database. Any and all ad 
>>> hoc, on the
>>> fly or unapproved changes just get summarily overwritten.
>>
>>
>> And you do this with users connected?  ;-)
>>

> I assume he means the development database. i.e. refresh the development
> database with the current production (or other appropriate phase) code.
>
> Developers need to learn to start the day by reapplying their current
> working changes. The mostly do.

 From my experience they mostly play in a sandbox that hasn't been cleaned in ages. Think Change Management policies the enemy of creative expression, and rarely understand what they are doing beyond some memorized syntax. I said "mostly."

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)
Received on Sun Mar 06 2005 - 11:17:51 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US