Quoth Oliver Schneider <oli...@f-prot.com>, on 2010-09-09 00:12:43 +0000: > > 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.
As something of an aside, if by "tampered with" you mean you are trying to protect from intentional unauthorized modification via an audit trail, SQLite may not provide the sort of hard security you want unless you are very careful and apply other mechanisms as well; it tends to be best used where arbitrary access to an entire database is within a single domain of authority. Just something to be aware of, especially since you mention command-line SQLite usage in the same paragraph. ---> Drake Wilson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
