On 4/23/2014 12:26 PM, Peter Hardman wrote:
Igor, thanks for your suggestion, but I'm using a trigger partly to prevent the user faking the timestamp.
If that's the concern, then if you find a mechanism by which an update made by your trigger isn't logged, the user would be able to use that same mechanism to make her own change that isn't logged.
You could have a default, and a BEFORE INSERT trigger that errors out if the timestamp is wrong.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
