On Wed, Mar 13, 2013 at 11:48 AM, David King <dk...@ketralnis.com> wrote: >> BTW, in case you don't do that yet your best performance will be if >> you prepare your UPDATE and INSERT statements only once and then do >> bind + step + reset in that 100k times loop. > > > In principle I agree, but since the temporary-table version is blindingly > fast up the the update-the-disk portion it's definitely not a bottleneck at > this point
I was talking about your initial implementation when you did 100k times > update_counter(k1, k2, count=count+1, expires=now+count*1day) > if rows_updated != 1: insert_counter(k1, k2, count=1, expires=now+1day) Not about your final version with one INSERT OR REPLACE. Was your statement about the same thing? If yes I didn't understand what you meant. Pavel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
