From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Imeev Mergen <imeevma@tarantool.org>,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 1/3] sql: EXPLAIN through net.box leads to SEGFAULT
Date: Wed, 28 Nov 2018 15:36:51 +0300 [thread overview]
Message-ID: <6552029A-67C7-4466-95BA-B9D0FFA57C57@tarantool.org> (raw)
In-Reply-To: <1542920122.851013557@f398.i.mail.ru>
That’s why I don’t like any verbal agreements…
My point is if result-set features column names,
then those columns must have type. I fail to come up with
example where resulting set features column names,
but columns don’t have types.
On the other hand, mb it is worth to send type ANY instead of
UNKNOWN, it makes sense to a greater or lesser extent.
> On 22 Nov 2018, at 23:55, Мерген Имеев <imeevma@tarantool.org> wrote:
>
> After discussion we decided that this patch will serve us
> part of patch-set that should close newly filed bug:
> https://github.com/tarantool/tarantool/issues/3832
>
> The main Idea behind this ticket is that any statement
> should return column type for when it returns column name.
> And this ticket allow us to find an error without falling
> into SEGMENTATION FAULT or returning less metadata.
>
> Четверг, 22 ноября 2018, 21:31 +03:00 от Vladislav Shpilevoy <v.shpilevoy@tarantool.org>:
>
> It was just a question, "why did you decide to do not
> send type". It was not necessary to start sending UNKNOWN. I
> think, that unknown type should be sent never.
next prev parent reply other threads:[~2018-11-28 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 13:47 [tarantool-patches] [PATCH 0/3] A set of small SQL fixes Vladislav Shpilevoy
2018-11-19 13:47 ` [tarantool-patches] [PATCH 1/3] sql: EXPLAIN through net.box leads to SEGFAULT Vladislav Shpilevoy
2018-11-19 17:27 ` [tarantool-patches] " n.pettik
2018-11-22 18:08 ` Imeev Mergen
2018-11-22 18:31 ` Vladislav Shpilevoy
2018-11-22 20:55 ` [tarantool-patches] Re[2]: " Мерген Имеев
2018-11-23 6:04 ` [tarantool-patches] Re: Re[2]: " Kirill Yukhin
2018-11-28 12:36 ` n.pettik [this message]
2018-11-29 14:58 ` [tarantool-patches] " Konstantin Osipov
2018-11-19 13:47 ` [tarantool-patches] [PATCH 2/3] sql: SELECT from system spaces returns unpacked msgpack Vladislav Shpilevoy
2018-11-19 17:27 ` [tarantool-patches] " n.pettik
2018-11-22 18:09 ` Imeev Mergen
2018-11-27 8:51 ` n.pettik
2018-11-19 13:47 ` [tarantool-patches] [PATCH 3/3] sql: too many autogenerated ids leads to SEGFAULT Vladislav Shpilevoy
2018-11-19 17:27 ` [tarantool-patches] " n.pettik
2018-11-22 18:09 ` Imeev Mergen
2018-11-27 8:50 ` n.pettik
2018-11-27 10:09 ` [tarantool-patches] Re: [PATCH 0/3] A set of small SQL fixes Kirill Yukhin
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=6552029A-67C7-4466-95BA-B9D0FFA57C57@tarantool.org \
--to=korablev@tarantool.org \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH 1/3] sql: EXPLAIN through net.box leads to SEGFAULT' \
/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