On Thu, 7 May 2015 11:25:33 -0500 John McKown <john.archie.mckown at gmail.com> wrote:
> On Thu, May 7, 2015 at 10:01 AM, Stephen Chrzanowski > <pontiac76 at gmail.com> wrote: > > > Although I can understand the sarcasm you're sending out, a > > client/server infrastructure would be an interesting task for > > SQLite to do, but to answer the OP, no, SQLite isn't inherently > > designed to be a client/server. > > > > ?And not really that difficult. Embed SQLite into some "server code" > to which a client connects, probably via TCPIP or some other IPC > method.? The client connects to the server, which uses the embedded > SQLite to access the appropriate SQLite data base file. I would guess > that the server could even be multi-threaded with each thread > controlling a separate SQLite data base file. Do you mean create a NewSQL Shared-Nothing distributed database with SQlite3, using something like nanomsg or 0MQ for distribute workload and messages, and Graph Theory for manage the whole headless distributed server? Don't try to do that. It's far complex than you think and even Pandora won't open it. I see now Stephen answer and he cite some of the problems you may encounter at "There are MANY things to be taken care of,.." paragraph. --- --- Eduardo Morras <emorrasg at yahoo.es>
