[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Against sqlite3!!!
From: |
Tassilo Horn |
Subject: |
Re: Against sqlite3!!! |
Date: |
Tue, 07 Dec 2021 16:51:22 +0100 |
User-agent: |
mu4e 1.7.5; emacs 29.0.50 |
Hi Hong,
I'm not very knowledgable with cl-* stuff but doesn't your
implementation load all key-value pairs at once? That would be quite a
disadvantage compared to a DB approach where I'd naturally expect that
only the value I'm asking for is loaded.
Also, how would it ensure consistency when I have 2 parallel emacs
sessions (like one for mail/irc and one for programming/editing) where
session 1 modifies the value of key A and the other of key B? It looks
like the values of the kv-store that gets saved later will win. In case
that's the emacs session which has modified B, it'll revert A to the
state before the other session modified it, no?
If that were true, I'd say your resist!.el is a non-starter in the
current form. It should at least load only values explicitly asked for
and only persist/override actually changed values. A trivial solution
could use one file per key. Not sure how sensible that is.
Bye,
Tassilo
Re: Against sqlite3!!! (Was: sqlite3), Zhu Zihao, 2021/12/07