Keith Medcalf <kmedcalf@...> writes: > ... you can create a trigger that adds the rowid of > rows inserted (ie, that you need to update) into another table.
Using trigger during insert slows down insert by about 20%. This is not much, but unnecessary as long as AUTOINCREMENT does not reach the maximum value. As other people mentioned, this is unlikely to happen in our lifetime. But if it will, then this trigger/second table approach may be a solution. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
