From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org, "Мерген Имеев" <imeevma@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 1/1] sql: IS is only applicable when dealing with NULL
Date: Sat, 19 May 2018 00:37:31 +0300 [thread overview]
Message-ID: <aa003384-af01-c2c0-5fb6-4f7c3342edb7@tarantool.org> (raw)
In-Reply-To: <1526659840.883327245@f345.i.mail.ru>
Hello. Thanks for the fixes! You did a huge work fixing the tests!
> >
> > -%include {
> > - /* A routine to convert a binary TK_IS or TK_ISNOT expression into a
> > - ** unary TK_ISNULL or TK_NOTNULL expression. */
>
> 3. I still can grep ISNULL token. NOTNULL too. They must be removed completely, but
> very accurately. For example, TK_NULL, TK_ISNULL, TK_NOTNULL are not tokens, they
> are identifiers for 'NULL', 'IS NULL', and 'IS NOT NULL'. But strings 'ISNULL' and
> 'NOTNULL' must be removed. For example, look extra/mkkeywordhash.c:196. Here all the
> tokens are stored and their identifiers, so "NOTNULL" is reflected into TK_NOTNULL.
> We must remove "NOTNULL". Same in parse.y:137, 213.
>
> In treeview.c:475 NOTNULL must be replaced with "NOT NULL". Same in vdbeaux.c:1508.
>
> Same about ISNULL.
>
> Partially done. Ones in parse.y used to generate identifiers to operations 'IS NULL' and 'IS NOT NULL'
I see, but they now are unused by parser. Please, remove them. The parser uses not "NOTNULL" or
"ISNULL" - it uses TK_ISNULL and TK_NOTNULL. Look at addopcodes.sh how to add TK_... constants
with no adding them to parser.
In the final patch you must not be able to grep "ISNULL" or "NOTNULL" strings anywhere.
By removal of these parser-unused things you will make the parser slightly faster.
The rest of the patch is ok.
next prev parent reply other threads:[~2018-05-18 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 11:26 [tarantool-patches] " Мерген Имеев
2018-05-18 11:55 ` [tarantool-patches] " Vladislav Shpilevoy
2018-05-18 16:10 ` [tarantool-patches] " Мерген Имеев
2018-05-18 21:37 ` Vladislav Shpilevoy [this message]
2018-05-23 14:30 ` Imeev Mergen
2018-05-24 11:52 ` Vladislav Shpilevoy
2018-05-24 14:00 ` Imeev Mergen
2018-05-24 19:46 ` Vladislav Shpilevoy
2018-05-30 8:35 ` Kirill Yukhin
2018-05-18 14:34 ` Konstantin Osipov
-- strict thread matches above, loose matches on Subject: below --
2018-05-16 13:50 [tarantool-patches] " Мерген Имеев
2018-05-16 18:52 ` [tarantool-patches] " Vladislav Shpilevoy
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=aa003384-af01-c2c0-5fb6-4f7c3342edb7@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/1] sql: IS is only applicable when dealing with NULL' \
/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