Re: [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by SET

[Nikita Pettik <korablev@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.