Re: Version control of Oracle Stored Objects.

On Sun, 6 Mar 2005 09:28:32 +0000, Jim Smith <jim_at_jimsmith.demon.co.uk> 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.

Once a developers walked in: "ok, implementation of requierement <xyz> may be delivered. you find all changed objects in some of the dev databases."

He had to run very fast!

--
Marc Blum
mailto:blumNOSPAM_at_marcblum.de
http://www.marcblum.de