From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 33835430407 for ; Tue, 11 Aug 2020 01:22:06 +0300 (MSK) References: <05992d38-6a4a-4e2e-db6e-041c4184d7e7@tarantool.org> From: Vladislav Shpilevoy Message-ID: <648d4151-3035-cadb-bf87-c3b01c40593f@tarantool.org> Date: Tue, 11 Aug 2020 00:22:04 +0200 MIME-Version: 1.0 In-Reply-To: <05992d38-6a4a-4e2e-db6e-041c4184d7e7@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH 0/2] JSON field multikey crash List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aleksandr Lyapunov , tarantool-patches@dev.tarantool.org, korablev@tarantool.org Hi! On 10.08.2020 12:10, Aleksandr Lyapunov wrote: > Hi! thanks for the patch. > Btw, why do we call them 'JSON fields'? Is it supposed that it should work somehow > with Java Script Object Notation serialization format? Yes. This is what JSON means. In context of this patch it is meant 'JSON field access'. Access of a tuple field by a JSON path.