Thanks Ryan - a handy summary. Food for thought.
Thanks, Chris On Fri, Oct 27, 2017 at 11:57 AM, R Smith <[email protected]> wrote: > > On 2017/10/27 11:52 AM, Bart Smissaert wrote: > >> Is this BedrockDB something that could be used to connect to a server and >> run SQL and avoid the problems (mainly slowness) that SQLite would >> have in this situation? >> > > and > > Chris Locke wrote: > My work environment is mainly Windows servers/users. SQLite 'works' but is > obviously unsupported (file locking, etc). > Could BedrockDb help in this area? Sounds like it works 'locally' but > 'networkably' (is that a word?!) Couldn't find any Windows-friendly builds > or guides. > Even assuming it could be set up, it also looks like there aren't .Net > drivers or 'wrappers' for it? > > > > This is not directly a client-server architecture, but you can achieve the > same result by having a server with a DB node and a local node that you > connect to locally, so you simply talk to your local node which in turn > communicates to the server. The main difference between that and a > client-server setup is that you experience no latency whatsoever, to your > app it's as-if the server exists on the local machine (which is technically > exactly the case), and of course the full dataset exists in two places, > locally and on the server (at least 2, but it is recommended to have 3 > places), which may be unwanted if local storage is really tight, but then > SQLite would also not have worked for you. > > [snipped] > Anyway, that's how we do it. > > Cheers, > Ryan _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
