From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f65.google.com (mail-lf1-f65.google.com [209.85.167.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 3386A46970F for ; Wed, 27 Nov 2019 14:39:19 +0300 (MSK) Received: by mail-lf1-f65.google.com with SMTP id f16so16900249lfm.3 for ; Wed, 27 Nov 2019 03:39:19 -0800 (PST) Date: Wed, 27 Nov 2019 14:39:17 +0300 From: Konstantin Osipov Message-ID: <20191127113917.GD9233@atlas> References: <20191127105150.GA7232@atlas> <20191127110532.GA16764@tarantool.org> <20191127111030.GB9233@atlas> <20191127112436.GB16940@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191127112436.GB16940@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by SET List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mergen Imeev Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org * Mergen Imeev [19/11/27 14:27]: > > But how are you going to fix it? By making SET statement powerful > > enough to query a value or by making the sysview updatable? > > > Since all settings are saved in a “struct session”, I > think that I will use the same methods PRAGMA used. The > system view reads from current_session(), so SET will > also read from there. OK, so you are going to allow SET to return an existing value, without setting it. Then what is the point of having a view, if you can both get and set the values using SET statement? -- Konstantin Osipov, Moscow, Russia