On Friday, April 3, 2015 at 9:18:39 PM UTC-7, Hiroyuki Sato wrote:
Hello jeremy.
Thank you for your comment.
I wrote test program.
It run two readers and writers. It access same table.
Almost operation complete 0.005 sec.
But sometime raise SQLite3::BusyException.
so It take over
On Friday, April 3, 2015 at 2:49:46 AM UTC-7, Hiroyuki Sato wrote:
Hello members.
Question
I'm using Sequel with Celluloid(https://celluloid.io)
Celluloid is a multithread library for Ruby.
And SQLite db is the file database. not on-memory db.
I got SQLite3
Hello members.
Question
I'm using Sequel with Celluloid(https://celluloid.io)
Celluloid is a multithread library for Ruby.
And SQLite db is the file database. not on-memory db.
I got SQLite3::BusyException, so I would like to avoid this exception.
It is possible to access
Hello jeremy.
Thank you for your comment.
I wrote test program.
It run two readers and writers. It access same table.
Almost operation complete 0.005 sec.
But sometime raise SQLite3::BusyException.
so It take over 5sec. (red part).
I have no idea why this operation lock database over
