Paxdo 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).

Something like <>.

See git or fossil, where the current state of the entire repository is
identified by a hash over all data and all previous changes; once a hash
value has been published, it is not possible to change anything without
changing the hash value.  (You need to save the hash values of the
interesting revisions somewhere else to be able to check them.)

These tools work on files, not on database objects.  But you could put
the entire database file in the repository.

sqlite-users mailing list

Reply via email to