From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp41.i.mail.ru (smtp41.i.mail.ru [94.100.177.101]) (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 9C7D1430D59 for ; Mon, 28 Oct 2019 10:55:39 +0300 (MSK) Date: Mon, 28 Oct 2019 10:55:37 +0300 From: Kirill Yukhin Message-ID: <20191028075537.f6he5m4jxo4dqud7@tarantool.org> References: <14cb474f-6cfd-7e16-e03d-bcade19d7bb2@tarantool.org> <20191027175035.GA72058@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20191027175035.GA72058@tarantool.org> Subject: Re: [Tarantool-discussions] Use _vsession_settings sysview to fetch session-local settings. List-Id: Tarantool development process List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikita Pettik Cc: server-dev@tarantool.org, Imeev Mergen , tarantool-discussions@dev.tarantool.org, Vladislav Shpilevoy , sergos@tarantool.org, Alexander Turenko Hello, On 27 окт 20:50, Nikita Pettik wrote: > On 24 Oct 18:39, Imeev Mergen wrote: > > Hi all, > > > > earlier, we decided to create sysview, which can be used to view > > SQL parameters and is not tied to any system space. It should > > create tuples with these settings on the fly. Now I suggest > > using this sysview to retrieve all the local session settings, not > > just the SQL settings. The only problem is that checking the > > uniqueness of the settings names is quite problematic. This > > problem can be solved by adding the prefixes "sql_", "vinyl_", > > etc. to the settings. I believe that in the same part of the > > project there will not be two or more parameters with the same > > name. > > > > In fact, we currently have no other session-local settings other > > than SQL settings. However, if I am not mistaken, they will appear > > in the future. > > > > What do you thiks about this? > > > > I'm okay with that, but I guess it shouldn't be prio 1 feature > of 2.3 release. I agree, let's postpone it to 2.4. -- Regards, Kirill Yukhin