From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <korablev@tarantool.org>
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 24BA646970F
 for <tarantool-patches@dev.tarantool.org>;
 Thu, 28 Nov 2019 17:01:05 +0300 (MSK)
Date: Thu, 28 Nov 2019 17:01:02 +0300
From: Nikita Pettik <korablev@tarantool.org>
Message-ID: <20191128140102.GA52457@tarantool.org>
References: <20191127105150.GA7232@atlas>
 <20191127110532.GA16764@tarantool.org>
 <20191127111030.GB9233@atlas>
 <20191127112436.GB16940@tarantool.org>
 <20191127113917.GD9233@atlas>
 <20191127122138.GB29304@tarantool.org>
 <CAPZPwLp2hL7BNKozOs_NLo0jg1k4CfKDGwYrNCKF49skgNreXA@mail.gmail.com>
 <20191127130156.GA31045@tarantool.org>
 <73e0d8e6-3bd3-3807-732a-32dfe5790466@tarantool.org>
 <20191128123120.GB29714@atlas>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191128123120.GB29714@atlas>
Subject: Re: [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by
 SET
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, Mergen Imeev <imeevma@tarantool.org>, tarantool-patches@dev.tarantool.org, kyukhin@tarantool.org, alexander.turenko@tarantool.org

On 28 Nov 15:31, Konstantin Osipov wrote:
> But you can easily work this around by lua('') generic built-in
> function, you can do lua('box.sql.exeucte("set <value")')
> 
> BTW, this lua() function is very neat - it is a good enough
> workaround for
> anything-you-want-to-have-in-sql-but-have-no-native-keyword-for.

Kostantin, you contradict yourself:

'''

From: Konstantin Osipov <kostja@scylladb.com>
...

* Nikita Pettik <korablev@tarantool.org> [19/09/11 20:34]:
> As I already said, we can move all these settings to box.sql submodule.
> To query particular value from SQL we can use new Lua() function:
>
> SELECT LUA("return box.sql.count_changes")

Why should the two language frontends be dependent on each other?
I mean, imagine we have JS support,would you want to call from JS
to Lua to configure some JS feature?
'''

'''

Date: Thu, 12 Sep 2019 14:18:56 +0300
From: Konstantin Osipov <kostja.osipov@gmail.com>
...

* Nikita Pettik <korablev@tarantool.org> [19/09/12 14:17]:
> The only way to make settings language independent (as I see) is to
> put them into separate system space (as I suggested below).

I don't mind an own space for settings at all. MySQL performance
schema is managed this way. It's a very flexible approach.

'''

We've started developing view approach to unify access and setting process
of SQL related options, like :update() and :select() operations.