3 ms·
> I don't think that's true. I think it's largely a matter of interpretation. To me, transactions imply atomicity, isolation and consistency, but not durabilit
by StavrosK 11y ago
> I don't think that's true.
I think it's largely a matter of interpretation. To me, transactions imply atomicity, isolation and consistency, but not durability (e.g. in-memory datastores can still support transactions). I can see your point, though.
> One could benchmark a non-ACID datastore against SQLite but only if each ran in an in-memory database mode.
Yep, or you can just turn fsync off. This is an option in most databases, to trade performance off for durability.
> the results from SQLite and Vedis in particular appear to be meaningful to compare.
Yep, Vedis seems to fsync after every commit, so I think you're right.
> requires that you ship the code to "any accompanying software that uses the DB software".
Ah, damnit, that's prohibitive. I didn't notice that, thanks, I thought they only required the source for modifying Vedis itself. rlite looks better, I think.