From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tarantool-patches-bounce@freelists.org>
Received: from localhost (localhost [127.0.0.1])
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 664B72B03F
	for <tarantool-patches@freelists.org>; Thu, 29 Nov 2018 09:58:39 -0500 (EST)
Received: from turing.freelists.org ([127.0.0.1])
	by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rzAxr8SBBvW0 for <tarantool-patches@freelists.org>;
	Thu, 29 Nov 2018 09:58:39 -0500 (EST)
Received: from smtp52.i.mail.ru (smtp52.i.mail.ru [94.100.177.112])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id C4ADD2AFA5
	for <tarantool-patches@freelists.org>; Thu, 29 Nov 2018 09:58:38 -0500 (EST)
Date: Thu, 29 Nov 2018 17:58:35 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 1/3] sql: EXPLAIN through net.box
 leads to SEGFAULT
Message-ID: <20181129145835.GC20244@chai>
References: <cover.1542635129.git.v.shpilevoy@tarantool.org>
 <f5a6d3d2-b4bf-cbfb-e53c-b128ad497538@tarantool.org>
 <6104171d-f355-733c-d01b-016127ec389a@tarantool.org>
 <1542920122.851013557@f398.i.mail.ru>
 <6552029A-67C7-4466-95BA-B9D0FFA57C57@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6552029A-67C7-4466-95BA-B9D0FFA57C57@tarantool.org>
Sender: tarantool-patches-bounce@freelists.org
Errors-to: tarantool-patches-bounce@freelists.org
Reply-To: tarantool-patches@freelists.org
List-help: <mailto:ecartis@freelists.org?Subject=help>
List-unsubscribe: <tarantool-patches-request@freelists.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: tarantool-patches <tarantool-patches.freelists.org>
List-subscribe: <tarantool-patches-request@freelists.org?Subject=subscribe>
List-owner: <mailto:>
List-post: <mailto:tarantool-patches@freelists.org>
List-archive: <http://www.freelists.org/archives/tarantool-patches>
To: tarantool-patches@freelists.org
Cc: Imeev Mergen <imeevma@tarantool.org>, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>

* n.pettik <korablev@tarantool.org> [18/11/28 15:51]:
> 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.

It would make sense if there was ANY type in SQL. Until there is
no support for ANY in SQL it's better to convert all results to
use only supported types - integer and string.

-- 
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov