On May 8, 2019, at 10:30 AM, Jose Isaias Cabrera <jic...@outlook.com> wrote:
>
> Warren Young, on Wednesday, May 8, 2019 12:10 PM, wrote...
>
>> How about you give up on the idea of using Windows shares to distribute a
>> SQLite DB
>> and use a tool meant for the job, such as BedrockDB?
>>
>> https://bedrockdb.com/
> Man, I wish this tool was available back in 2007.
My sense — as an outsider — is that the codebase is almost that old, but that
it was closed-source until late 2016.
Here’s a couple of threads on this list about it:
http://sqlite.1065341.n5.nabble.com/Introducing-Bedrock-SQLite-for-the-Enterprise-td92037.html
http://sqlite.1065341.n5.nabble.com/BedrockDB-interview-on-Floss-Weekly-td98256.html
> Gotta try it with cygwin.
According to one of the core devs, it shouldn’t be difficult to port it to
build against the standard Windows API:
https://github.com/Expensify/Bedrock/issues/66
A scan of their PR queue shows they accept the majority of those they receive.
As to whether it’s worth the effort, I doubt you can measure a response time
difference between a Cygwin binary and a pure Windows API binary unless you’re
going beyond gigabit speeds. The thickest part of Cygwin is the fork()
emulation, and that’s only used once in Bedrock on server startup to implement
the -fork option, which you’d want to do differently on Windows anyway.
(A truly native Windows version would have an option to allow running it as a
Windows Service.)
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
