From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Imeev Mergen <imeevma@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 1/6] sql: remove unnecessary macros from pragma.*
Date: Mon, 24 Dec 2018 16:01:33 +0200 [thread overview]
Message-ID: <82E2786D-D829-4950-AE7D-6094955EE4D4@tarantool.org> (raw)
In-Reply-To: <5e5daaaeb306feae8caf3af98a3708431c58062e.1544871594.git.imeevma@gmail.com>
Nit: at the end of commit subject redundant ‘*’ and dot.
> On 15 Dec 2018, at 13:54, imeevma@tarantool.org wrote:
>
> Some of the macros used in pragma.c and pragma.h are obsolete
> because the values they checked were deleted.
They weren’t deleted, they are simply not used.
I guess they still can be enabled, if add appropriate commands
to cmake lists. On the other hand, I doubt that someday we
really may need them.
> Part of #3832
In fact, this commit has nothing in common with mentioned issue.
> -#if !defined(SQLITE_OMIT_FLAG_PRAGMAS)
> { /* zName: */ "query_only",
> /* ePragTyp: */ PragTyp_FLAG,
> /* ePragFlg: */ PragFlg_Result0 | PragFlg_NoColumns1,
> @@ -168,28 +157,23 @@ static const PragmaName aPragmaName[] = {
> /* ePragFlg: */ PragFlg_Result0 | PragFlg_NoColumns1,
> /* ColNames: */ 0, 0,
> /* iArg: */ SQLITE_RecTriggers},
> -#endif
> -#if !defined(SQLITE_OMIT_FLAG_PRAGMAS)
> { /* zName: */ "reverse_unordered_selects",
> /* ePragTyp: */ PragTyp_FLAG,
> /* ePragFlg: */ PragFlg_Result0 | PragFlg_NoColumns1,
> /* ColNames: */ 0, 0,
> /* iArg: */ SQLITE_ReverseOrder},
> -#endif
> -#if !defined(SQLITE_OMIT_FLAG_PRAGMAS) && defined(SQLITE_ENABLE_SELECTTRACE)
> +#if defined(SQLITE_ENABLE_SELECTTRACE)
Why didn’t you remove ENABLE_SELECTTRACE as well?
> @@ -254,8 +231,7 @@ static const PragmaName aPragmaName[] = {
> /* ColNames: */ 0, 0,
> /* iArg: */ SQLITE_VdbeTrace},
> #endif
> -#endif
> -#if !defined(SQLITE_OMIT_FLAG_PRAGMAS) && defined(SQLITE_ENABLE_WHERETRACE)
> +#if defined(SQLITE_ENABLE_WHERETRACE)
The same question.
next prev parent reply other threads:[~2018-12-24 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 11:51 [tarantool-patches] [PATCH v2 0/6] sql: set column types for EXPLAIN and PRAGMA imeevma
2018-12-15 11:54 ` [tarantool-patches] [PATCH v2 1/6] sql: remove unnecessary macros from pragma.* imeevma
2018-12-20 20:41 ` [tarantool-patches] " Vladislav Shpilevoy
2018-12-24 14:01 ` n.pettik [this message]
2018-12-15 11:56 ` [tarantool-patches] [PATCH v2 2/6] sql: fix "PRAGMA parser_trace" result imeevma
2018-12-24 14:01 ` [tarantool-patches] " n.pettik
2018-12-15 12:01 ` [tarantool-patches] [PATCH v2 3/6] sql: Show currently set sql_default_engine imeevma
2018-12-24 14:01 ` [tarantool-patches] " n.pettik
2018-12-15 12:03 ` [tarantool-patches] [PATCH v2 4/6] sql: fix "PRAGMA case_sensitive_like" result imeevma
2018-12-24 14:01 ` [tarantool-patches] " n.pettik
2018-12-15 12:05 ` [tarantool-patches] [PATCH v2 5/6] sql: 'PRAGMA' result in Tarantool format imeevma
2018-12-24 14:02 ` [tarantool-patches] " n.pettik
2018-12-15 12:08 ` [tarantool-patches] [PATCH v2 6/6] sql: set column types for EXPLAIN and PRAGMA imeevma
2018-12-24 14:02 ` [tarantool-patches] " n.pettik
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=82E2786D-D829-4950-AE7D-6094955EE4D4@tarantool.org \
--to=korablev@tarantool.org \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2 1/6] sql: remove unnecessary macros from pragma.*' \
/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