Thanks for your reply.
> Can't you just include the modified value within your UPDATE or
> INSERT statement? Or is the modified column in a separate table?
Guess I'll do that. SQLite is just so convenient even from command line,
that I thought it'd be better to automate that part to figure out if the
data set was tampered with.
> It sounds like your triggering on ANY table update, not the specific
> table you're interested in.
Hmm, strange. These are the triggers I used:
CREATE TRIGGER IF NOT EXISTS file_change AFTER UPDATE OF hash,name,path
ON file
BEGIN
UPDATE file SET modified=julianday('now');
END;
CREATE TRIGGER IF NOT EXISTS file_insert AFTER INSERT ON file
BEGIN
UPDATE file SET modified=julianday('now');
END;
// Oliver
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
