I have several such applications, running in industrial environment.
I always use a TCP server on 'X' and TCP client on 'Y' with some simple,
specialized http-like protocol on top.
All this can be implemented very easy, especially if you don't need a top
performance and millions of clients. In addition such solution allows to avoid
complex settings with web servers, back-front ends etc. The server and the
client are built in the desktop application and the communication is
transparent for the users.
On Thu, 11 Jan 2018 09:06:32 +0000
James Colehan <jcole...@gtt-training.com> wrote:
> I am looking for some advice on using SQLite for my given situation.
> My system involves a windows network. On PC 'X', I have an SQLite database
> with a process that handles amendment's to the database ie INSERTS, DELETES
> and UPDATES. Also, on PC 'X' I have some other processes running that are
> requesting data (SELECT) form the database. I have the Journal Mode set to
> WAL. This all appears to work fine.
> My concern is that I have a requirement to query the database on PC 'X' from
> other PC's. Basically, performing (SELECT) statements from stations 'Y' and
> 'Z'. This creates a client/server situation that I appreciate SQLite is not
> appropriate choice of database for. I hope doing the (SELECT) only from the
> client will be a workable solution.
> At the moment I have not encountered any problems. However, my concern is
> that this maybe just luck and there is a potential of locking issues or
> database corruption.
> Any thoughts would be appreciated.
> sqlite-users mailing list
John Found <johnfo...@asm32.info>
sqlite-users mailing list