From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 127C827492 for ; Wed, 18 Jul 2018 11:37:13 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mTxmUFwgBAIm for ; Wed, 18 Jul 2018 11:37:12 -0400 (EDT) Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id A9BAD220A8 for ; Wed, 18 Jul 2018 11:37:12 -0400 (EDT) Received: by mail-lj1-f195.google.com with SMTP id q5-v6so4477133ljh.12 for ; Wed, 18 Jul 2018 08:37:12 -0700 (PDT) MIME-Version: 1.0 References: <1530533500-9666-1-git-send-email-hollow653@gmail.com> <20180717135933.cc2g7rlbb2xl4kgo@tkn_work_nb> <07E4F387-E976-432B-A80B-E01B40BCF126@corp.mail.ru> In-Reply-To: <07E4F387-E976-432B-A80B-E01B40BCF126@corp.mail.ru> From: Nikita Tatunov Date: Wed, 18 Jul 2018 18:37:00 +0300 Message-ID: Subject: [tarantool-patches] Re: [PATCH] sql: assertion fail on nested select Content-Type: multipart/alternative; boundary="0000000000000d2e4d057147d6ac" Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-subscribe: List-owner: List-post: List-archive: To: n.pettik@corp.mail.ru Cc: tarantool-patches@freelists.org, alexander.turenko@tarantool.org --0000000000000d2e4d057147d6ac Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I woudln't consider it as an actual 'fix' though. =D1=81=D1=80, 18 =D0=B8=D1=8E=D0=BB. 2018 =D0=B3. =D0=B2 18:17, n.pettik@co= rp.mail.ru : > > I tried to test that problem on this sqlite3 version with -DSQLITE_DEBUG > and assertion fails there. > Since flattening only makes another compound select-stmt with ORDER BY > clause I guess error was > occuring on flattened version of it. Moreover in latter versions of > sqlite3 this assert was deleted and the > restriction check wasn't fixed. So I assume sqlite3 developers just don't > know about it or don't aim on > fixing it as the error anyways occurs but on flattened subquery. > > > Here is original fix of this assertion fail (JFYI): > https://www.sqlite.org/src/info/823779d31eb09cda > > --0000000000000d2e4d057147d6ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I woudln't consider it as an actual 'fix' thou= gh.

=D1=81=D1=80, 18 = =D0=B8=D1=8E=D0=BB. 2018 =D0=B3. =D0=B2 18:17, n.pettik@corp.mail.ru <n.pettik@corp.mail.ru>:

I tried to test that prob= lem on this sqlite3 version with -DSQLITE_DEBUG and assertion fails there.= =C2=A0
Since flattening only makes another compound select-stmt w= ith ORDER BY clause I guess error was
occuring on flattened versi= on of it. Moreover in latter versions of sqlite3 this assert was deleted an= d the
restriction check wasn't fixed. So I assume sqlite3 dev= elopers just don't know about it or don't aim on
fixing i= t as the error anyways occurs but on flattened subquery.
<= /div>

Here is original fix of this assertio= n fail (JFYI):

--0000000000000d2e4d057147d6ac--