From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 6465E45C304 for ; Sun, 13 Dec 2020 21:30:28 +0300 (MSK) References: <2bcd06c2ee8f5fcfdb8e2d0d640ab822362832f7.1607696813.git.lvasiliev@tarantool.org> From: Vladislav Shpilevoy Message-ID: <93f47160-4a9b-da02-71a0-8e757b3f1ac7@tarantool.org> Date: Sun, 13 Dec 2020 19:30:25 +0100 MIME-Version: 1.0 In-Reply-To: <2bcd06c2ee8f5fcfdb8e2d0d640ab822362832f7.1607696813.git.lvasiliev@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH v2 2/3] sql: set an error to diag in sql_execute() on failure List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Leonid Vasiliev , imeevma@tarantool.org, korablev@tarantool.org, sergos@tarantool.org, m.semkin@corp.mail.ru Cc: tarantool-patches@dev.tarantool.org Thanks for the patch! I agree with Nikita here. The change is dangerous. If there is no a diag, but the query failed, it means something is very wrong, and it is not safe to continue execution. A panic() would be better here.