That's not quite correct. The data can be altered, as long as you record who altered it and how. We do this in our primary database (Oracle). How it works is that that any user who uses the interface must log in (username and password). Then any transaction they initiate is recorded including their username. So all of our tables have associate transactions logs that record what the value was, what the value was changed to, when was this done and by whom.
So it's not that dbms don't handle this yet. But not many web applications have needed this level of security to date. If you are building an e-record system from scratch, take a look at banking and medical database technology for your cues. They have been dealing with this level of sophistication for decades.
--------------
Ian Skinner
Web Programmer
BloodSource
www.BloodSource.org
Sacramento, CA
"C code. C code run. Run code run. Please!"
- Cynthia Dunning
Confidentiality Notice: This message including any
attachments is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the
intended recipient, please contact the sender and
delete any copies of this message.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
