Re: how to design versioning?

Good response, Richard. Tom Kyte demonstrated just recently in this newsgroup an example of this new feature. You can also find an example in the official Oracle docs.

Take a look at Tom's words by doing a Google groups search on the subject of the thread ("tigger to store info on change"), being sure to quote this title exactly.
The misspelling was in the original thread. You'll find that Tom wrote his response last Thursday morning.

Bye,
TG

Richard Foote wrote:

> Hi David,
>
> I actually don't think it's quite what you're after but Oracle9i has a new
> Workspace Management feature that enables selected tables to be version
> enabled and for there to be different versions of the same logical row.
>
> It might be worth a peep at just in case there's something there for you.
>
> Cheers
>
> Richard
> "Daniel Morgan" <dmorgan_at_exesolutions.com> wrote in message
> news:3D8F3DAE.84B67418_at_exesolutions.com...
> > david chan wrote:
> >
> > > Hi,
> > >
> > > I need to versioning my data in a way so that all version of record
> > > can be retrived later on. I have about 15 tables and only records in
> > > one table need occasional versioning (probally once per month for some
> > > records in that table).
> > >
> > > I am thinking to add different version of records into same table but
> > > each record with a version date (so the record with nearest date is
> > > latest version).
> > > Is it a doable approach or anyone has different idea?
> > >
> > > Thanks.
> > > David
> >
> > Doable. But it not my method of preference.
> >
> > What I prefer is an AFTER UPDATE OR DELETE trigger on the table that
> > archives :OLD.field_names to a separate table along with the date-time and
> > user responsible for the update or deletion.
> >
> > Daniel Morgan
> >
Received on Tue Sep 24 2002 - 18:26:41 CDT