Thanks for your reply, Igor. Trigger is a solution, but it still has a efficient problem as I know. May be I'm wrong with this idea, so I would try trigger and do some benchmarks on it.
Still I wanna know is there another way to solve this problem, thanks. On Mon, Mar 26, 2012 at 8:00 PM, Igor Tandetnik <itandet...@mvps.org> wrote: > Wu Jian <ravinw...@gmail.com> wrote: > > then I exec a SQL like this UPDATE this_table SET data='abc' WHERE id > > 2. > > > > OK. We all know that row 3 and row 4 was updated by my SQL. But how > should > > my program know that? > > What does your program need to know that for? What do you plan to do with > this information? > > Would a trigger help? http://sqlite.org/lang_createtrigger.html > -- > Igor Tandetnik > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
