[sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
ther process will be allowed access to the database because I am going to open it in none sharing more. All access will be through the client API. So how do I make it so there is no locking? -- hls ___ sqlite-users mailing list sqlite-users@sqlite.org ht

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
my application to boost its performance). > > > Pavel > > On Tue, Mar 16, 2010 at 10:05 AM, HLS wrote: >> Folks, >> >> I read the documentation suggesting to use another SQL engine for a >> multi-threaded client/server environment and I reached a point where I

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
On Tue, Mar 16, 2010 at 11:54 AM, Olaf Schmidt wrote: > > "HLS" schrieb im > Newsbeitrag > news:9cf5931e1003160705v38335b5g47a3d91193c28...@mail.gmail.com... > >> ...we have a ISAM/BTREE database under our full >> reader/writer and exclusive locking controls

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
while readers > are active right away. Beware though that if you have open reading > cursor and trying to write over the same SQLite connection then your > transaction won't be committed until cursor is closed. > > > Pavel > > On Tue, Mar 16, 2010 at 11:36 AM, HLS

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
On Tue, Mar 16, 2010 at 1:01 PM, HLS wrote: > >   dim f as TFileRecord >   dim tid as integer >   dim n as integer = 0 >   LoginSystem() >   if GetFirstFileRec(FileNameAreaKey, f, tid) then >      do >       inc(n) >      ... do something ... >      loop while Get

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
been looking at the feasibility of changing code (which is the last thing I don't want to do.) On Tue, Mar 16, 2010 at 1:31 PM, Simon Slavin wrote: > > On 16 Mar 2010, at 5:17pm, HLS wrote: > >> Once approach is to queue any updates/deletes when the database is >> locked with

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
to 1. If you don't use shared > cache and turned off locking on VFS level then you can easily get > database corruption. > > Pavel > > On Tue, Mar 16, 2010 at 2:12 PM, HLS wrote: >> Thanks Simon.  It just seem so simplistic that SQLITE3 does not allow for >> &g

Re: [sqlite] SQLITE3 in multi-thread server

2010-03-16 Thread HLS
On Tue, Mar 16, 2010 at 4:44 PM, Simon Slavin wrote: > One of the things that makes SQLite very simple is that it doesn't try to do > this, it has either everything or nothing locked. Yes, that is coming to realization now. -- hls ___ s