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 A7F1827B23 for ; Thu, 19 Jul 2018 06:48:44 -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 P-1j0gcy0Q8h for ; Thu, 19 Jul 2018 06:48:44 -0400 (EDT) Received: from smtp47.i.mail.ru (smtp47.i.mail.ru [94.100.177.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 6631527B11 for ; Thu, 19 Jul 2018 06:48:44 -0400 (EDT) Date: Thu, 19 Jul 2018 13:48:42 +0300 From: Kirill Yukhin Subject: [tarantool-patches] Re: [PATCH v1 1/1] sql: raise error for DELETE FROM nonexistent table Message-ID: <20180719104842.qcse2toaexm5qq2r@tarantool.org> References: <8ea2b4731ccf9d79140d17f87a6a1ed05f9948d8.1531753721.git.kshcherbatov@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ea2b4731ccf9d79140d17f87a6a1ed05f9948d8.1531753721.git.kshcherbatov@tarantool.org> 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: tarantool-patches@freelists.org Cc: korablev@tarantool.org, Kirill Shcherbatov Hello, On 16 июл 18:09, Kirill Shcherbatov wrote: > Parser didn't raise error when DELETE FROM can't find > a table specified on statement. > As no error was raised, partially-prepared VDBE code > seemed to be generated fine, that was not true. > > Closes #3535. > --- > Branch: https://github.com/tarantool/tarantool/compare/kshch/gh-3535-assertion-on-delete > Issue: https://github.com/tarantool/tarantool/issues/3535 I've checked in your patch into 2.0 branch. -- Regards, Kirill Yukhin