Sure, SQLite isn't as heavier hitter as pg et al. But I've seen it handle
millions of records (although perhaps not "more than a few Gb of data" without
too much trouble.
I guess I was thinking it would be nice to have interchangeable backends for
any new Leo db backend, and if you were going that route you could use SQLite
for simplicity until such time as you needed to switch to something better. I
wouldn't expect Kent to hit gigabytes of data very quickly, at least not in
dev. stages.
Cheers -Terry
From: Mike Hodson <[email protected]>
To: [email protected]
Sent: Monday, March 6, 2017 1:56 PM
Subject: Re: Well Kent, your vision for Leo is becoming clearer
On Mon, Mar 6, 2017 at 12:26 PM, 'Terry Brown' via leo-editor
<[email protected]> wrote:
Hi - I wouldn't discount SQLite either, DB wise, unless you need connect to a
*remote* server capability, but for local work it's quite capable. And a
proper abstraction layer should make it possible to switch out the backend.
Cheers -Terry
Hi Terry, I've got another quick "Mike's $0.02" relating to SQLite..
I've found that a local SQL Server, (My/Maria/MS/pg) is nearly "required" when
dealing with data larger than a few gigabytes, and further, the optimizations
in Maria/pg allow for very quick querying and joining of the data as well,
evidenced by my hundreds-of-thousands-of-emails in KMail working properly with
Maria and working very sporadically with sqlite. (when working for a webhosting
company where _everything_ (tickets/alerts/daily notifications/vendor
mails/*.*) was emailed out to _everyone_.)
However I've yet to compare with a more capable and perhaps better programmed
project that has utilized mysql/pgsql and also has proper sqlite integration;
from my understanding, the coding model is very different and this may be a
reason the KDE people haven't optimized for sqlite and/or bugs exist in the
code as nobody uses sqlite fully knowing the mysql akonadi integration "just
works"
R1Soft CDP, the backup solution, has since version 3.0 used a SQLite database
file as its "block storage" and every successful merge of old recovery points
causes a full-sqlite-file-rewrite-to-disk. I am strong in my belief that if
they used Maria or Postgres instead of SQLite, they'd have a far more
performant product and less filesystem fragmentation with 'file per table'
XtraDB layout in Maria, or whatever Postgres does internally to be so bloody
efficient.
Mike
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
