On 7 Sep 2017, at 9:16am, Paxdo <pa...@mac.com> wrote:
> For security reasons, a customer wants to be sure that a database line cannot > be modified after its initial insertion (or unmodified without being visible, > with proof that the line has been modified). Including by technicians who can > open the database (SQLITE of course). Is there a difference between "modified" and "deleted and then a new one put in" ? Either way, you should be able to do something like this with UPDATE and DELETE TRIGGERs which causes the new command to fail. They could do this by violating a constraint, or by division by zero, or referring to a table which didn’t exist. Those things should cause SQLite to crash or return a failure code rather than successfully replacing the original record. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
