Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Version control of Oracle Stored Objects.
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.
-- Jim Smith Because of their persistent net abuse, I ignore mail from these domains (among others) .yahoo.com .hotmail.com .kr .cn .tw For an explanation see <http://www.jimsmith.demon.co.uk/spam>Received on Sun Mar 06 2005 - 03:28:32 CST
![]() |
![]() |