Re: "Write once-Read many" table ?
From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Tue, 04 Mar 2008 20:36:23 +0100
Message-ID: <b6548$47cda4b7$524b5c40$27646@cache3.tilbu1.nb.home.nl>
>
> In fact, business management want to be sure that a line inserted will
> never be changed, by anyone.
> They would like a feature to ensure that.
> Something that would be guaranteed by construction in the database,
> guaranteed by oracle ...
>
> I ask the question on their behalf.
>
> Thanks
Date: Tue, 04 Mar 2008 20:36:23 +0100
Message-ID: <b6548$47cda4b7$524b5c40$27646@cache3.tilbu1.nb.home.nl>
jm.scheiwiler_at_gmail.com wrote:
> On Feb 28, 2:46 pm, Mladen Gogala <mgog..._at_yahoo.com> wrote:
>> On Thu, 28 Feb 2008 03:17:19 -0800, jm.scheiwiler wrote: >>>> You have to trust your DBA. That's the bottom line. >>>> --http://mgogala.freehostia.com >>> The thing is, I am the dba. >>> I trust myself but that's not enough >> So, who else, besides you, can do grants & revokes? >> >> -- >> Mladen Gogalahttp://mgogala.freehostia.com
>
> In fact, business management want to be sure that a line inserted will
> never be changed, by anyone.
> They would like a feature to ensure that.
> Something that would be guaranteed by construction in the database,
> guaranteed by oracle ...
>
> I ask the question on their behalf.
>
> Thanks
Create a tablespace (e.g. "jms") with an associated (new!) datafile.
Create your table (e.g. "ro_table") in tablespace "jms".
Put tablespace "jms" in read-only mode.
Burn a copy of the datafile onto a good-quality
read-only media (e.g. WORM).
Mount the read-only (WORM?) device
Tell Oracle the datafile has been moved.
Drop the original datafile.
Unless you reverse the process, and mount a new copy, changes are impossible. Costs a whole lot less than Data Vault :)
-- Regards, Frank van Bortel Top-posting in UseNet newsgroups is one way to shut me upReceived on Tue Mar 04 2008 - 13:36:23 CST