From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] sql: remove tests on ORDER BY/LIMIT + DELETE
Date: Mon, 11 Feb 2019 22:00:57 +0300 [thread overview]
Message-ID: <3E8E578A-52BB-496C-B448-4C2DEDAA0E05@tarantool.org> (raw)
In-Reply-To: <20190211130953.GC20767@chai>
> On 11 Feb 2019, at 16:09, Konstantin Osipov <kostja@tarantool.org> wrote:
>
> * n.pettik <korablev@tarantool.org> [19/02/09 08:47]:
>>> Why ever delete tests? Why not let them (expectedly) fail?
>> Could you please clarify the purpose of such tests?
>
> In this particular case I don't entirely rule out the possibility
> of these features re-appearing in our product.
Are you kidding? It was you who supported idea of removing
this feature:
‘’'
You can always use WHERE pk IN (subquery expr) - this is the standard alternative.
ORDER BY ... LIMIT is only useful if your optimizer is very weak, otherwise you can do it efficiently with a standard compliant SQL, in relational spirit.
‘''
But OK, even if we decided to enable this thing, it wouldn’t
be possible without implementing it from a scratch.
Almost all code related to ORDER BY + DELETE was
removed a long ago, only a few lines remained.
And even those lines haven’t been kept up to date
during numerous refactoring/reworking patches
(aka dead code). Hence, those tests are completely
useless and there is no chance that they will be turned on
again someday.
prev parent reply other threads:[~2019-02-11 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 15:34 [tarantool-patches] " Ivan Koptelov
2019-02-04 15:50 ` [tarantool-patches] " n.pettik
2019-02-04 19:11 ` Ivan Koptelov
2019-02-05 13:42 ` n.pettik
2019-02-07 17:45 ` i.koptelov
2019-02-07 18:54 ` n.pettik
2019-02-08 14:22 ` n.pettik
2019-02-08 17:38 ` Konstantin Osipov
2019-02-08 19:16 ` n.pettik
2019-02-11 13:09 ` Konstantin Osipov
2019-02-11 19:00 ` n.pettik [this message]
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=3E8E578A-52BB-496C-B448-4C2DEDAA0E05@tarantool.org \
--to=korablev@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] sql: remove tests on ORDER BY/LIMIT + DELETE' \
/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