Re: [sqlite] SPHiveDB: A server for sqlite database.

"lau stephen" schrieb im Newsbeitrag news:c26a05160906150443h44b8f434s46e6ab4215f61...@mail.gmail.com... 2009/6/14 Olaf Schmidt : >> Each client could do (with a 1:10 relation of writes and reads) >> >> Loop 1000 times >> With LoopCounter Modulo 7

Re: [sqlite] SPHiveDB: A server for sqlite database.

2009/6/14 Olaf Schmidt : > Interesting approach - (such a mem-vfs offers some nice > options at the serverside, once it is done). > > Did you already tested, how the whole approach behaves > in concurrency-scenarios with e.g. only 4-8 concurrent clients? > Using your schema,

Re: [sqlite] SPHiveDB: A server for sqlite database.

"Olaf Schmidt" schrieb im Newsbeitrag news:h131eu$m0...@ger.gmane.org... > Loop 1000 times > With LoopCounter Modulo 7 (case-switch) > ... > ... > Ending up with 11 new records in the DB Ok - make the loop-counter 7000 to reach the result of 11 new records.

Re: [sqlite] SPHiveDB: A server for sqlite database.

"stephen liu" <stephen@gmail.com> schrieb im Newsbeitrag news:e5a33d590906140609h4f3f35fah9083be3560f5d...@mail.gmail.com... http://code.google.com/p/sphivedb/ > SPHiveDB is a server for sqlite database. It use JSON-RPC over > HTTP to expose a network interface

[sqlite] SPHiveDB: A server for sqlite database.

http://code.google.com/p/sphivedb/ SPHiveDB is a server for sqlite database. It use JSON-RPC over HTTP to expose a network interface to use SQLite database. It supports combining multiple SQLite databases into one file. It also supports the use of multiple files ( through Tokyo Cabinet