On Tue, Dec 20, 2011 at 10:17 PM, Thomas Mueller < [email protected]> wrote:
> Hi, > > > why is adding a content_hash column to the relevant tables not an option? > > That wouldn't prevent you from deleting rows, and re-adding previously > deleted rows. > Yes. While one can prevent re-adding of rows if table has a primary key is of type identity and this is used to compute the hash, I do not see can one can have proof of unauthorized deletion of rows. BTW, I've tried (unsuccessfully) to make something like tamper-proof tables (records, as I see now) using computed columns here: http://pastie.org/3051925 Some of the behavior/errors do not look exactly OK to me, but since I have no use for it right now, I'm not that concerned. On the other hand, tamper-proof tables/records may be a nice feature to have and if H2 Roadmap is not big enough... -- Regards, Vasile Rotaru -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
