From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 18 Jul 2019 14:20:35 +0300 From: Kirill Yukhin Subject: Re: [tarantool-patches] [PATCH v3 1/4] box: introduce key_def->is_multikey flag Message-ID: <20190718112035.imj7wfmzczhld6ba@tarantool.org> References: <90d806637a4a9ccb48285beff02b3400d7058f07.1563326037.git.kshcherbatov@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <90d806637a4a9ccb48285beff02b3400d7058f07.1563326037.git.kshcherbatov@tarantool.org> To: tarantool-patches@freelists.org Cc: vdavydov.dev@gmail.com, kostja@tarantool.org, Kirill Shcherbatov List-ID: Hello, On 17 Jul 04:20, Kirill Shcherbatov wrote: > Previously only key definitions that have JSON paths were able > to define multikey index. We used to check multikey_path != NULL > test to determine whether given key definition is multikey. > In further patches with functional indexes this rule becomes > outdated. Functional index extracted key definition may be > multikey, but has no JSON paths. > So an explicit is_multikey flag was introduced. > > Needed for #1260 I've checked the patch into master. -- Regards, Kirill Yukhin