On 3 Sep 2019, at 5:34pm, Alexander Vega <amve...@mail.usf.edu> wrote:
> sqlite3_open("database1", &db1);
> sqlite3_open("database1", &db2);
Bear in mind that SQLite is not a server/client DBMS. The database is not kept
in memory (unless you arrange this explicitly). All operations have to wait
for the storage that holds the database.
So yes, you can open two connections. But it's not going to magically double
the speed of your program.
> // do SELECT on db1
> // do UPDATE on db2
Do you expect the SELECT to see the results of the previous UPDATE ? It won't,
until the transaction has ended (unless you arrange this explicitly).
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
