Re: Version Control

From: Alan Johnson <alan.johnson_at_gel.com>
Date: 1998/03/19
Message-ID: <351103F4.AD75A7F0_at_gel.com>#1/1

All of these suggestions seem to be handling source code control outside the database (which, admittedly is where it usually is). Does anyone have any suggestions that embed the versioning inside the database. Specifically, as stored procedures change, previous versions are kept, such that referential integrity between a set of data and the stored procedure used to process the data at the time of instantiation can be maintained. I'm thinking a journal on the system table(s) that store the source for the stored procs, but if there is somethig better, please let me know.

Alan

Matthias Gresz wrote:

> On Tue, 10 Mar 1998 07:34:02 -0600, kirtt_at_sky.net (Kirt Thomas) wrote:
> Hi,
>
> for triggers, procs and packages take a look at platinum's SQL-Station at www.platinum.com.
>
> >I'm curious regarding what you folks are using for version control
> >software -
Received on Thu Mar 19 1998 - 00:00:00 CET

This message: [ Message body ]
Next message: Michael Krolewski: "Re: dynamically called a stored procedure from proC?"
Previous message: Neil and Tracey Mooney: "HELP!"
Maybe in reply to: Kirt Thomas: "Version Control"
In reply to Matthias Gresz: "Re: Version Control"
Next in thread: Michael Krolewski: "Re: dynamically called a stored procedure from proC?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message