From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp54.i.mail.ru (smtp54.i.mail.ru [217.69.128.34]) (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 E0D264696C3 for ; Fri, 3 Apr 2020 21:11:14 +0300 (MSK) From: "Timur Safin" References: <8dc7be67-fc78-dd42-0634-83692259f0a5@ocelot.ca> In-Reply-To: <8dc7be67-fc78-dd42-0634-83692259f0a5@ocelot.ca> Date: Fri, 3 Apr 2020 21:11:12 +0300 Message-ID: <016601d609e3$42b82980$c8287c80$@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Language: ru Subject: Re: [Tarantool-patches] [PATCH 0/4] session settings fixes List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: 'Peter Gulutzan' , tarantool-patches@dev.tarantool.org : From: Peter Gulutzan : : Re: : SETTING SET "sql_default_engine" = 'memtx'; : : Adding a new reserved word SETTING, without advance notice, : should be against policy. It causes a slight risk : of breaking an existing application. : : I had hoped for : UPDATE _SETTINGS_DEFAULT_ENGINE SET VALUE = 'memtx'; : I claim that is just as "user friendly" -- it : adds two words, but it removes quotation marks. : And it does not require that users learn new syntax : because UPDATE ... SET is well known. Yes, I like this way `UPDATE config SET VALUE = value` - it's looking very natural for SQL, without any unnecessary extension of a language whatsoever. Timur