Re: [sqlite] Client/Server Best Practices

Clients know nothing about the database, they just submit a request and get results. The server is the only process accessing and using SQLite. Rick Kelly -- View this message in context: http://sqlite.1065341.n5.nabble.com/Client-Server-Best-Practices-tp79728p79731.html Sent from the SQLite

Re: [sqlite] Client/Server Best Practices

On 25 Dec 2014, at 12:32pm, Rick Kelly wrote: > If a request encounters %SQLITE_BUSY or %SQLITE_LOCKED, I'm retrying up to 5 > times with a 100ms sleep in between. > > Will this approach minimize %SQLITE_BUSY and %SQLITE_LOCKED situations and > provide decent concurrency and

Re: [sqlite] Client/Server Best Practices

On Thu, Dec 25, 2014 at 7:32 AM, Rick Kelly wrote: > I'm using SQLite3 for the first time and am looking to see if those more > experienced can look at my deployment and offer suggestions. > > I have a client/server application running on MS Windows communicating over > TCP/IP

[sqlite] Client/Server Best Practices

I'm using SQLite3 for the first time and am looking to see if those more experienced can look at my deployment and offer suggestions. I have a client/server application running on MS Windows communicating over TCP/IP supporting a few dozen clients. Basically, clients send a request to the server