From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>,
Bruno Thomsen <bth@kamstrup.com>
Subject: Re: [ptxdist] [PATCH] sqlite: enable foreign keys by default
Date: Fri, 21 Feb 2020 12:41:33 +0100 [thread overview]
Message-ID: <20200221114133.o3pm3bqoik7e47i7@pengutronix.de> (raw)
In-Reply-To: <CAH+2xPDzysTPKfj+JEQyC3Ggg0sUcUtQSH=91H=z8Nf3gJipFg@mail.gmail.com>
On Fri, Feb 21, 2020 at 12:20:33PM +0100, Bruno Thomsen wrote:
> Hi Michael
>
> Den fre. 21. feb. 2020 kl. 08.23 skrev Michael Olbrich
> <m.olbrich@pengutronix.de>:
> >
> > On Sat, Feb 15, 2020 at 01:52:05PM +0100, Bruno Thomsen wrote:
> > > Support for foreign_keys pragma was already enabled at
> > > compile-time, but it was not enabled by default on new
> > > database connections. It's still possible to turn off
> > > enforcement at runtime.
> > > This makes it easier to work on databases that uses
> > > this feature without causing them to end up in an
> > > invalid state.
> >
> > Hmm, what's the impact of this? What are the performance implications? And
> > what's the default in other distros? I mean, if the default is generally
> > off, then I don't expect any existing software to disable this.
>
> Fedora 31 has =0, I don't know about other distros,
> but you can test it fast with an in-memory database.
>
> $ sqlite3
> sqlite> pragma foreign_keys;
> 1
> sqlite> .exit
FTR: on Debian the pragma command yields 0. (Tested with sqlite3
3.31.1-2 that is currently in testing/unstable)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2020-02-21 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 12:52 Bruno Thomsen
2020-02-21 7:23 ` Michael Olbrich
2020-02-21 11:20 ` Bruno Thomsen
2020-02-21 11:41 ` Uwe Kleine-König [this message]
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=20200221114133.o3pm3bqoik7e47i7@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.com \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox