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

Konstantin Osipov kostja.osipov at gmail.com
Wed Nov 27 14:10:30 MSK 2019


* Mergen Imeev <imeevma at tarantool.org> [19/11/27 14:07]:
> > Usually, if one allows SET statement, SET option_name (without 
> > "= new_value") prints the current setting. This does the job and
> > makes the "_vsettings" system view unnecessary.
> > 
> > Don't you think that having to use one piece of syntax to query a
> > value and entirely different piece to assign it is, ehm,
> > inconsistent, hard to learn & remember, and eventually hard to
> > use?
> > 
> You are right. This was also pointed by Vlad in previous
> review:
> "2. Ok, but now it looks really unusable when a user want's to
> learn an option value. I will create a ticket, if this patchset
> will be pushed and nobody will care about usability beforehand."

But how are you going to fix it? By making SET statement powerful
enough to query a value or by making the sysview updatable?

Either way you fix it, the second patch will become unnecessary,
don't you think?

> Personally, I think this is easy to fix, and your
> suggestion is good. In fact, I can fix this in this
> patch-set if Vlad and Nikita agree with this solution.

-- 
Konstantin Osipov, Moscow, Russia


More information about the Tarantool-patches mailing list