From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Nikita Pettik <korablev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by SET
Date: Thu, 28 Nov 2019 00:50:23 +0300 [thread overview]
Message-ID: <20191127215023.GA31812@atlas> (raw)
In-Reply-To: <20191127140317.GA56049@tarantool.org>
* Nikita Pettik <korablev@tarantool.org> [19/11/27 17:34]:
>
> It may sound trite but why not look at other DBs? For instance,
> PosgtreSQL uses SHOW command, which looks OK personally to me.
> Or alternatively why can't we simply use _sql_settings:select("default_engine")?
> In this case SHOW will be purely SQL shortcut for :select().
Seriously?-) This sounds like some sort of joke?
I did suggest to look at other DBMS serveral times, in fact the
most widely used DBMS in the world, sqlite, which happens to use
pragmas!
Once again, other dbms are a good source of inspiration, but in
the end of the day one has to have a *different* criteria for
product design, and it is what is the mission of *this* product
and what it is trying to accomplish.
> > 2) Should we remove _vsession_settings from the problem.
>
> What is the problem? What are alternatives?
>
> > 3) If we move sysview out of the problem, where should we move it.
>
> What do you mean by "move sysview out of the problem"?
>
> Could you please clarify last two question.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-11-27 21:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 10:13 [Tarantool-patches] [PATCH 0/5] Introduce SQL SET statement imeevma
2019-11-27 10:13 ` [Tarantool-patches] [PATCH 1/5] sql: remove PRAGMA "count_changes" imeevma
2019-11-27 10:13 ` [Tarantool-patches] [PATCH 2/5] sql: remove PRAGMA "short_column_names" imeevma
2019-11-27 10:13 ` [Tarantool-patches] [PATCH 3/5] temporary: disable boolean.test.sql imeevma
2019-11-27 10:13 ` [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by SET imeevma
2019-11-27 10:45 ` Mergen Imeev
2019-11-27 10:51 ` Konstantin Osipov
2019-11-27 11:05 ` Mergen Imeev
2019-11-27 11:10 ` Konstantin Osipov
2019-11-27 11:24 ` Mergen Imeev
2019-11-27 11:39 ` Konstantin Osipov
2019-11-27 12:21 ` Mergen Imeev
2019-11-27 12:49 ` Konstantin Osipov
2019-11-27 13:01 ` Mergen Imeev
2019-11-27 14:03 ` Nikita Pettik
2019-11-27 21:50 ` Konstantin Osipov [this message]
2019-11-27 23:22 ` Vladislav Shpilevoy
2019-11-28 12:31 ` Konstantin Osipov
2019-11-28 14:01 ` Nikita Pettik
2019-11-28 15:52 ` Konstantin Osipov
2019-11-27 23:18 ` Vladislav Shpilevoy
2019-11-27 10:13 ` [Tarantool-patches] [PATCH 5/5] sql: refactor PRAGMA-related code imeevma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191127215023.GA31812@atlas \
--to=kostja.osipov@gmail.com \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 4/5] sql: replace control pragmas by SET' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox