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 960B744643B for ; Sat, 26 Sep 2020 01:58:22 +0300 (MSK) References: From: Vladislav Shpilevoy Message-ID: <51245d8c-9fe4-b185-ecaf-93e1144115f5@tarantool.org> Date: Sat, 26 Sep 2020 00:58:21 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH 12/14] WIP: module api: expose box_key_def_merge() List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-patches@dev.tarantool.org Thanks for the patch! Why would a module need that function? Its usage case is very specific - merge primary and secondary parts to create a unique key def for non-unique indexes. Is there a case outside of the storage engines for that function?