> On Sep 7, 2017, at 9:31 AM, Simon Slavin <slav...@bigfraud.org> wrote:
> 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.
That can be bypassed by editing the raw file data, without going through
SQLite, so I'm assuming it wouldn't be secure enough for the OP.
sqlite-users mailing list