Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

> From: Free Ekanayaka, on Thursday, August 29, 2019 10:21 AM, wrote... > > Hello Jose, > > Jose Isaias Cabrera, on > > which lets me know that it linux/unix based. But, is Windows an > > option also? Thanks. > > At the moment Windows is not an option, mainly because under the hood > dqlite

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

Hi Dominique, Dominique Devienne writes: > On Thu, Aug 29, 2019 at 2:35 PM Jose Isaias Cabrera > wrote: > >> Free Ekanayaka, on Thursday, August 29, 2019 06:40 AM, wrote... >> > See https://dqlite.io for more details. >> >> Can dsqlite be installed on Windows? I went to the site, read the >>

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

Hello Jose, Jose Isaias Cabrera writes: > Free Ekanayaka, on Thursday, August 29, 2019 06:40 AM, wrote... >> >> Hi, >> >> following up from my previous post back in 2017 [0], I'd like to >> announce version 1.0.0 of dqlite, a C library that brings data >> replication and high-availability to

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

On Thu, Aug 29, 2019 at 2:35 PM Jose Isaias Cabrera wrote: > Free Ekanayaka, on Thursday, August 29, 2019 06:40 AM, wrote... > > See https://dqlite.io for more details. > > Can dsqlite be installed on Windows? I went to the site, read the > README.md file, and could not find any reference of

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

Free Ekanayaka, on Thursday, August 29, 2019 06:40 AM, wrote... > > Hi, > > following up from my previous post back in 2017 [0], I'd like to > announce version 1.0.0 of dqlite, a C library that brings data > replication and high-availability to SQLite, using the Raft consensus > algorithm. > >

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

Hello, I updated the FAQ [0] with your two questions. Free [0] https://github.com/canonical/dqlite/blob/master/doc/faq.md#why-c test user writes: > Hey Free, > > Looks like an interesting project. > > Is there a blog or docs about the reasons for the move from Go to C? > > Also what types of

Re: [sqlite] dqlite 1.0.0 - SQLite replication and failover library

Hey Free, Looks like an interesting project. Is there a blog or docs about the reasons for the move from Go to C? Also what types of systems would utilise dqlite? Are there current users? Thanks On Thu, 29 Aug 2019 at 11:41, Free Ekanayaka wrote: > Hi, > > following up from my previous

[sqlite] dqlite 1.0.0 - SQLite replication and failover library

Hi, following up from my previous post back in 2017 [0], I'd like to announce version 1.0.0 of dqlite, a C library that brings data replication and high-availability to SQLite, using the Raft consensus algorithm. The biggest change is that Go is not used anymore, the engine itself is all pure C

Re: [sqlite] Replication

>>> An SQL database is deemed "Relational" when it can communicate >>> mildly ... SQL stands for Structured Query Language. It has nothing whatsoever to do with the data store but rather is a specification of the Language used to retrieve/manipulate the datastore. This is the same as "C" or

Re: [sqlite] Replication

Relational databases, and the Relational Model, are not so called because their records stand in relation to other records. The Model, and the subsequent databases, are about relations, which are a long-standing and precisely defined mathematical concept. So, I'm afraid, you are actually wrong

Re: [sqlite] Replication

On Fri, 12 Oct 2018 14:31:10 +0200, R Smith wrote: > > >> An SQL database is deemed "Relational" when it can communicate mildly > >> relational data using mildly relational (but mathematically sound) > >> methods. It doesn't need to be (nor claim to be) the Almighty keeper of > >> all

Re: [sqlite] Replication

An SQL database is deemed "Relational" when it can communicate mildly relational data using mildly relational (but mathematically sound) methods. It doesn't need to be (nor claim to be) the Almighty keeper of all relationality, nor even simply conform to various specific interpretations of the

Re: [sqlite] Replication

abase replication, but it doesn't need to be > general-purpose. Fossil's synchronization mechanism is custom-tailored > to its specific purpose. This is what I was actually saying. > If you were hoping to use Fossil as a general-purpose SQLite replication > system, then yeah, it's not g

Re: [sqlite] Replication

On Fri, 12 Oct 2018 00:06:38 +0200, R Smith wrote: > >> WARNING: the following sentence will be claimed to be controversial: >> >> No database based on SQL is truly relational. > > LOL - who would claim that to be controversial? > > It doesn't spur controversy... > > It's worthy of a shrug at

Re: [sqlite] Replication

On Thu, 11 Oct 2018 16:56:21 -0700, David Barrett wrote: > Incidentally, Bedrock is built on a blockchain as well -- though I agree > with the sentiment that blockchain isn't actually new at all, and not that > big of a deal. More information is here: > http://bedrockdb.com/blockchain.html

Re: [sqlite] Replication

Incidentally, Bedrock is built on a blockchain as well -- though I agree with the sentiment that blockchain isn't actually new at all, and not that big of a deal. More information is here: http://bedrockdb.com/blockchain.html Hope you enjoy it! -david On Thu, Oct 11, 2018 at 3:06 PM R Smith

Re: [sqlite] Replication

WARNING: the following sentence will be claimed to be controversial: No database based on SQL is truly relational. LOL - who would claim that to be controversial? It doesn't spur controversy... It's worthy of a shrug at best, perhaps a "So what?". It sounds like a deepity - much like any

Re: [sqlite] Replication

om the other side, > but it is exactly what Fossil needs. I agree that what Fossil does is not the same thing as general-purpose relational database replication, but it doesn’t need to be general-purpose. Fossil’s synchronization mechanism is custom-tailored to its specific purpose. If you we

Re: [sqlite] Replication

On Thu, 11 Oct 2018 14:37:47 -0600, "Keith Medcalf" wrote: > > Balderdash. > > > The interlocking of artifacts by cryptographic hashes does seem very much > > like the same idea as blockchain, which Wikipedia says was invented in > > 2008. It is interesting that the first Fossil checkin was 21

Re: [sqlite] Replication

Balderdash. > The interlocking of artifacts by cryptographic hashes does seem very much > like the same idea as blockchain, which Wikipedia says was invented in > 2008. It is interesting that the first Fossil checkin was 21 July, 2007 > (and the first git checkin was 7 April, 2005). Hashed

[sqlite] Replication

Picking up a couple of sentences from a different thread, just for a reference point really, please feel free to ignore ... On Thu, 11 Oct 2018 10:20:08 -0600, Warren Young wrote: > On Oct 11, 2018, at 12:26 AM, Darren Duncan wrote: 8>< >> This makes me think that it would be useful,

Re: [sqlite] dqlite - SQLite replication and failover library

Wout Mertens writes: > Oh I see, of course. So I assume the client library automatically sends > write commands to the current leader? No, that's up the application for now, the library just returns you an error if you attempt a write on a non-leader node. > I wonder if

Re: [sqlite] dqlite - SQLite replication and failover library

Oh I see, of course. So I assume the client library automatically sends write commands to the current leader? I wonder if there is value in setting a preferred leader, but probably that's messing too much with the Raft protocol. On Sun, Aug 20, 2017, 11:44 PM Free Ekanayaka

Re: [sqlite] dqlite - SQLite replication and failover library

Free Ekanayaka writes: >> And when not enough nodes are available, writes are hung until >> consensus? > > Yes, but there's a (configurable timeout). BTW, this is a consequence of Raft sitting in the CP spectrum of the CAP theorem: in case of a network partition it chooses

Re: [sqlite] dqlite - SQLite replication and failover library

Wout Mertens writes: > Very interesting! > > So how does it behave during conflict situations? Raft selects a winning > WAL write and any others in flight are aborted? Ah yeah this is probably something that was not clear from the docs or from my presentation. There

Re: [sqlite] dqlite - SQLite replication and failover library

to anyone needing a C/Rust > version. > > The work has been funded by Canonical, the company behind Ubuntu. Please > see the dqlite's home page [1] for more details. > > = SQLite replication API patch = > > This is the SQLite patch that dqlite depends on. It essentially

[sqlite] dqlite - SQLite replication and failover library

It should hopefully at least serve as reference to anyone needing a C/Rust version. The work has been funded by Canonical, the company behind Ubuntu. Please see the dqlite's home page [1] for more details. = SQLite replication API patch = This is the SQLite patch that dqlite depends on. It essent

Re: [sqlite] Sqlite replication

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wade Williams wrote: > In my research it appears SQLite may not be a good option, since the > only replication appears to be "lock the database and copy the file to > the new machine." Others have pointed out the simplicity of doing that. It is

Re: [sqlite] Sqlite replication

I would think that it would be even easier than that -- simply write a separate 20-line python script that starts a transaction (thus assuring that no one else is writing to the db while the file is being copied), then forks an rsync to copy the single database file to another file on the

Re: [sqlite] Sqlite replication

It would be a relatively minor job to make Sqlite replicate itself. The partitioning in its design seperates the i/o level. Wade Williams wrote: > I'm looking for an honest assessment from someone that may have made > this decision in the past. > > I'm considering using an embedded database

Re: [sqlite] Sqlite replication

although I'm not an sqlite expert (but using it since a few month) I'm wondering why you actually need that sqlite-internal recovery system: I understand that you have two servers running either parallel or one of them will switched on in case of a failure of the primary server, right ? I also

Re: [sqlite] Sqlite replication

PROTECTED] On Behalf Of Wade Williams Sent: quinta-feira, 11 de dezembro de 2008 14:32 To: sqlite-users@sqlite.org Subject: [sqlite] Sqlite replication I'm looking for an honest assessment from someone that may have made this decision in the past. I'm considering using an embedded database

[sqlite] Sqlite replication

I'm looking for an honest assessment from someone that may have made this decision in the past. I'm considering using an embedded database for an upcoming application. Operation rate is high 20,000-60,000 per day. (Those will mostly be selects, but some smaller percentage will be inserts).