On Monday 30 August 2004 4:08 pm, [EMAIL PROTECTED] wrote: > I think that INSERT-only would be as good as we could hope for as I have > been having a very hard time trying to think of a valid business reason > why a user would be allowed to either UPDATE or DELETE rows from a table > where they weren't allowed to even see the data. However I can think of > several business reasons for an INSERT-only table: >
The situation I have is like this. End User enters data in web page. Web page data is encrypted using mysql's aes_encrypt and stored in remote DB (not the same machine as the web server). If End User wants to update the data the new data is encrypted and overwrites the old (End User cannot see what old data was). If the db user account gets compromised via the web server (username and/or password gets disclosed/cracked/etc), the data (encrypted or not) cannot be retrieved via that account, only overwritten. > > UPDATE secrettable SET column = 'value'; > > DELETE FROM secrettable; > That may be possible, but I can't really see anywhere where that would be useful. Thanks. Todd -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
