From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alexandre Garreau Newsgroups: gmane.emacs.devel Subject: Re: sqlite3 Date: Wed, 15 Dec 2021 03:34:06 +0100 Message-ID: <2328395.9DzazV271f@galex-713.eu> References: <87tufmjyai.fsf@gnus.org> <2563341.DJk1cxha8W@galex-713.eu> <89627B39-5DC7-402E-9897-2708B7A5CC2B@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7001"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "larsi@gnus.org" , "emacs-devel@gnu.org" To: Qiantan Hong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 15 03:35:06 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mxK8I-0001eR-3I for ged-emacs-devel@m.gmane-mx.org; Wed, 15 Dec 2021 03:35:06 +0100 Original-Received: from localhost ([::1]:56244 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mxK8G-0004Bb-QE for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Dec 2021 21:35:04 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxK7S-0003VE-V5 for emacs-devel@gnu.org; Tue, 14 Dec 2021 21:34:14 -0500 Original-Received: from [2a00:5884:8305::1] (port=36490 helo=galex-713.eu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxK7R-0002iG-9n for emacs-devel@gnu.org; Tue, 14 Dec 2021 21:34:14 -0500 Original-Received: from gal by galex-713.eu with local (Exim 4.94.2) (envelope-from ) id 1mxK7L-002tMg-48; Wed, 15 Dec 2021 03:34:07 +0100 In-Reply-To: <89627B39-5DC7-402E-9897-2708B7A5CC2B@mit.edu> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:5884:8305::1 (failed) Received-SPF: pass client-ip=2a00:5884:8305::1; envelope-from=galex-713@galex-713.eu; helo=galex-713.eu X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:281967 Archived-At: Le merkredo, 15-a de decembro 2021 3-a horo kaj 18:53 CET, vous avez =C3=A9= crit=20 : > > What about having an intermediary abstraction for persistent stores in > > general, and on top of that multisession variables? >=20 > I think Lars=E2=80=99 multisession variable is basically a strict subset = of > persistent store, and can be implemented with almost trivial wrappers > if a persistent store interface is presented. No, from what I understood multisession *is* not a store (although it=20 *uses* one (or two, now)) but an implementation of persistent variables. Iiuc it doesn=E2=80=99t expose a stable abstraction layer for a kv-store, r= ight? > So if we do have a > persistent store interface, the multisession.el interface is > unnecessary. A more high-level/transparent persistent variable > interface, instead, is probably more desired. Why don=E2=80=99t you hack multisession so that it includes a such layer, b= etween=20 the current highest-level interface, the choice between sqlite/files? even= =20 before that, you could add your incremental-log-store to them, and also,=20 why not, at least for benchmark sake, a store where one file contains=20 everything such as custom.el > My plan, store.el + persist.el, follows exactly this direction. It seems > that the Emacs maintainers are unwilling to include them in place of > what they currently have, however, so guess we have to put it on Elpa > first. apparently they already have an implementation for that, maybe you should=20 work with theirs? at least it would advance I see no reason why ppl would use your implementation, even if it=E2=80=99s= more=20 richly designed, if it doesn=E2=80=99t provide something that=E2=80=99s ver= y new and not=20 already present. I find your incremental store interesting but not=20 appealing, while your abstraction still doesn=E2=80=99t allow using sqlite = as one=20 of its backends.