hi Darko,
>If you're preparing that statement more than once then you are wasting time, there's no reason whatsoever to do it. You're also wasting time if you make a bind call to set any column that hasn't changed since the last time you executed the statement. >The entire row is rewritten when updating so the most efficient way to do it is to call sqlite3_prepare_v2 once, then bind any columns that have changed, call sqlite3_step to execute the statement, then call sqlite3_reset to reuse the statement, then go back to binding any columns that have changed and repeat the other steps. sqlite3_reset does not clear any column bindings. Thanks for the explanation. It makes sense. Thanks Gaurav -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
