Oliver Schneider wrote: > I'm having a table of file names along with hashes and so on. In order > to make sure that we keep a record, I had put a trigger on UPDATE and > INSERT which would set the column 'modified' (REAL, Julian day) to the > time of the change. However, this slows down any INSERTs (even those > seemingly unrelated to this table) considerably. > > Is there a better method to achieve the same, i.e. keep track of when a > row was last changed?
Can't you just include the modified value within your UPDATE or INSERT statement? Or is the modified column in a separate table? It sounds like your triggering on ANY table update, not the specific table you're interested in. Nick.
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
