all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tim Cross <theophilusx@gmail.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Adding emacsql to NonGNU ELPA?
Date: Mon, 3 Jan 2022 16:00:31 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488BCD5FDCCABA59B639172F3499@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <877dbhrmst.fsf@gmail.com>

> concern is the treatment of 1:1 mapping between elisp nil and
> sql null. I'm not sure this is a good idea. In database terms, null is
> different from nil (or false). In database terms, null essentially means
> 'unknown' - it isn't false, it isn't true, it is unknown. Most databases
> also have a boolean value - perhaps for elisp, false would be a better
> mapping for nil than null?

+1.

(Caveat: I'm not following this thread.)

Good default relations between Lisp nil and SQL NULL,
and good user control over those relations, are very
important.

[The same is true for relations between JSON null and
SQL NULL, BTW.  Sometimes you want to treat them
similarly; sometimes (typically) you don't.  And when
you don't, you want to be able to specify just what
the relation (handling/transformation) is to be.]



  reply	other threads:[~2022-01-03 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 16:16 Adding emacsql to NonGNU ELPA? Stefan Kangas
2022-01-02 17:09 ` Teemu Likonen
2022-01-03 11:40 ` Lars Ingebrigtsen
2022-01-03 12:54   ` Tim Cross
2022-01-03 16:00     ` Drew Adams [this message]
2022-01-27  4:19   ` Tim Landscheidt
2022-01-27  6:03     ` Stefan Monnier
2022-01-27 14:54       ` Tim Landscheidt
2022-01-27 15:52         ` Stefan Monnier
2022-01-27 22:56     ` Tomas Hlavaty
     [not found]     ` <87bkzwyek6.fsf@logand.com>
     [not found]       ` <87h79obnuy.fsf@vagabond.tim-landscheidt.de>
2022-01-28 19:12         ` Tomas Hlavaty

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488BCD5FDCCABA59B639172F3499@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=theophilusx@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.