And huge speedup by exec("BEGIN") myloop exec("COMMIT")sob., 11 sty 2020 o 07:30 Andy <borucki.andr...@gmail.com> napisał(a): > I had sqlite3_prepare_v2 without sqlite3_finalize and sqlite3_close not > closes multiple databases. > > sob., 11 sty 2020 o 07:17 Andy <borucki.andr...@gmail.com> napisał(a): > >> These tests are a lot faster than calling Sqlite in my program, I must >> use the same convention: for example first prepare, next >> sqlite3_bind_int64, sqlite3_bind_text and sqlite3_step. My calling was very >> not optimal. >> >> pt., 10 sty 2020 o 20:13 Simon Slavin <slav...@bigfraud.org> napisał(a): >> >>> Are you aware of >>> >>> <https://www.sqlite.org/src/file/test/speedtest1.c> >>> >>> ? Now all you have to do is write comparative tests for other SQL >>> implementations. However, from what I've seen, realistic speed tests tend >>> to come down to cache sizes. >>> _______________________________________________ >>> sqlite-users mailing list >>> sqlite-users@mailinglists.sqlite.org >>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >>> >> _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
