开发者

Reader and writer process SQLite

开发者 https://www.devze.com 2022-12-21 17:18 出处:网络
I have two processes: Writes to two tables every second (ish) Reads from said tables periodically I know that with SQLite, any writes lock the whole database and so sometimes the second process ca

I have two processes:

  1. Writes to two tables every second (ish)
  2. Reads from said tables periodically

I know that with SQLite, any writes lock the whole database and so sometimes the second process can fail with a locked database.

Is there anything you can suggest that would completely remove the need for these two processes to touch the same database? For example, could I atomically transfer the data from the database being written 开发者_Python百科to a second read-only database?

Thanks :)


You can configure the connection to the database in the second process to wait for a certain time when it encounters a busy database, waking up periodically to check for a free database, before giving up.

sqlite3_busy_timeout(sqlite3*, int ms);

http://www.sqlite.org/c3ref/busy_timeout.html


May I suggest reading the FAQ on SQLite thread safety?

Threads are evil. Avoid them.

SQLite is threadsafe. We make this concession since many users choose to ignore the advice given in the previous paragraph. But in order to be thread-safe, SQLite must be compiled with the SQLITE_THREADSAFE preprocessor macro set to 1.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号