From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng2.m.smailru.net (smtpng2.m.smailru.net [94.100.179.3]) (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 95FF842EF5C for ; Thu, 18 Jun 2020 01:30:35 +0300 (MSK) References: From: Vladislav Shpilevoy Message-ID: Date: Thu, 18 Jun 2020 00:30:33 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH 0/3] box.execute() and box.cfg() idempotence and locking List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko , Igor Munkin Cc: tarantool-patches@dev.tarantool.org Generally the patchset is fine, except one commit for the last commit. However the 'feature' about implicit box.cfg call should be deleted, IMO. It only brings complexity to the code. No one ever asked for it. Its purpose was to allow to do box.cfg from SQL console, but there is no a problem in doing it manually before touching SQL. Anyway nobody uses box.cfg without parameters except for small manual tests. Note, box.execute('SELECT lua("box.cfg ...")') won't work, because VDBE and the parser heavily depend on the initialized box.