Re: [sqlite] An artificial query whose outcome is changed after left join reduction

0) To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] An artificial query whose outcome is changed after   left join reduction Off Topic Addendum: Last night I wrote up a new document [1] on why the SQLite project does not use Git.  The URL above (https

Re: [sqlite] An artificial query whose outcome is changed after left join reduction

On 4/10/18, E.Pasma wrote: > Hello, the nature of this case is purely artificial and I thought it > is worth considering in the light of real world problem as reported by > Raphael Michel. E Pasma > > .version > SQLite 3.23.0 2018-03-24 13:24:02 >

Re: [sqlite] An artificial query whose outcome is changed after left join reduction

? -Original Message- From: David Raymond Sent: Tuesday, April 10, 2018 10:41 AM To: SQLite mailing list Subject: RE: [sqlite] An artificial query whose outcome is changed after left join reduction That's weird. My compiled CLI for 3.23 gets what you're showing for 3.22 SQLite version 3.23.0 2018

Re: [sqlite] An artificial query whose outcome is changed after left join reduction

That's weird. My compiled CLI for 3.23 gets what you're showing for 3.22 SQLite version 3.23.0 2018-04-02 11:04:16 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> .version SQLite 3.23.0 2018-04-02