unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: built-in sqlite support in 29 - still time for changes?
Date: Tue, 21 Mar 2023 10:02:34 -0400	[thread overview]
Message-ID: <CAM=F=bDRrydumMf1e-Z4tVysQsc6HaeAYAq9JGEKHcJUsCzLKg@mail.gmail.com> (raw)
In-Reply-To: <83fs9y6xbx.fsf@gnu.org>

On Tue, Mar 21, 2023 at 9:35 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Lynn Winebarger <owinebar@gmail.com>
> > Date: Tue, 21 Mar 2023 09:18:16 -0400
> >
> > *  Is the current code mature enough to document properly, or is that
> > being delayed until the implementation is more mature?
>
> I'm not sure I understand what do you mean by "document properly",
> since the SQLite support is already documented in the ELisp reference
> manual.

That's user error on my part.  Even though I was running my last built
version of master, the last version of emacs I built/installed was
28.3, so I was seeing the old manual.
Thanks

> (I have no opinion on the other issues you raise.)

Would patches still be accepted for emacs-29?  I don't know what the
cutoff is.  For the first point in particular, I don't know if the
emacsql convention is the best, but it seems gratuitous to change the
idiom unless there's a good reason.  It seems like emacsql query
compiler could be adapted to the builtin support with the advantage of
not being restricted to string values, so existing code could be
conveniently ported.


Lynn



  reply	other threads:[~2023-03-21 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 13:18 built-in sqlite support in 29 - still time for changes? Lynn Winebarger
2023-03-21 13:36 ` Eli Zaretskii
2023-03-21 14:02   ` Lynn Winebarger [this message]
2023-03-21 14:15     ` Eli Zaretskii

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='CAM=F=bDRrydumMf1e-Z4tVysQsc6HaeAYAq9JGEKHcJUsCzLKg@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).