From: Thierry Volpiatto <thievol@posteo.net>
To: Qiantan Hong <qhong@mit.edu>
Cc: Alexandre Garreau <galex-713@galex-713.eu>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Against sqlite3!!!
Date: Thu, 09 Dec 2021 19:16:57 +0000 [thread overview]
Message-ID: <878rwt1tcm.fsf@posteo.net> (raw)
In-Reply-To: <9B4512CF-55D3-4619-95B8-0AA30C3E7F47@mit.edu> (Qiantan Hong's message of "Thu, 9 Dec 2021 07:50:18 +0000")
Qiantan Hong <qhong@mit.edu> writes:
>> If you start dividing your file into pages and loading one page at a time,
>> you’re starting to reimplement a kv-database, just as gdbm (or some
>> filesystems). You’d better reuse gdbm,
> There is a subtle but IMO significant benefit of resist!, it understands
> more than kv-put. In the current version, it also understands
> kv-push and kv-delete (aka list operations).
>
> I imagine this can be very useful for Lisp because lots of time people
> just add or remove data from a list. Some implementation that doesn’t
> understand this would need to dump the whole list again.
>
>> and work on something higher level
>> and more fun like a lisp sql-like query language, inspired from (or even
>> compatible with) sql or sparql or prolog, except each expression would
>> return a lisp value. That would be very beautiful.
> That’s definitely a cool idea. I’ll probably just go for an embedded Prolog
> with S-exp syntax.
>
> It’s probably not my current priority though, because
> Emacs packages at the moment still use mostly LISt Processing,
> and somehow people still find enough incentive to introduce SQLite3,
> which I attribute to the lack of a decent pure Lisp persistent store.
Emacs-lisp provide eval-when-compile which allows saving elisp objects
in compiled files, I use this since years to save my variables in emacs.
See psession package.
--
Thierry
next prev parent reply other threads:[~2021-12-09 19:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR12MB3391BC76A0D05236AC76C94E946E9@MN2PR12MB3391.namprd12.prod.outlook.com>
2021-12-07 8:13 ` Against sqlite3!!! (Was: sqlite3) Qiantan Hong
2021-12-07 9:14 ` Qiantan Hong
2021-12-07 12:49 ` Against sqlite3!!! Colin Baxter 😺
2021-12-07 13:21 ` Stefan Monnier
2021-12-07 13:55 ` Qiantan Hong
2021-12-07 15:51 ` Tassilo Horn
2021-12-07 16:35 ` Qiantan Hong
2021-12-07 18:43 ` Arthur Miller
2021-12-07 19:13 ` Qiantan Hong
2021-12-07 19:34 ` Tassilo Horn
2021-12-08 10:00 ` Yuri Khan
2021-12-07 19:52 ` Stefan Monnier
2021-12-07 13:45 ` Against sqlite3!!! (Was: sqlite3) Zhu Zihao
2021-12-07 14:50 ` Against sqlite3!!! David Engster
2021-12-07 20:00 ` Lars Ingebrigtsen
2021-12-08 6:11 ` Arthur Miller
2021-12-08 6:20 ` Qiantan Hong
2021-12-08 9:21 ` Arthur Miller
2021-12-08 9:28 ` Qiantan Hong
2021-12-09 7:12 ` Alexandre Garreau
2021-12-09 7:27 ` Qiantan Hong
[not found] ` <24465971.J1OoJ6LT5i@galex-713.eu>
2021-12-09 7:50 ` Qiantan Hong
2021-12-09 19:16 ` Thierry Volpiatto [this message]
2021-12-09 19:24 ` Qiantan Hong
2021-12-09 19:28 ` Qiantan Hong
2021-12-09 13:17 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rwt1tcm.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
--cc=qhong@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).