From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng1.m.smailru.net (smtpng1.m.smailru.net [94.100.181.251]) (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 381EC43D678 for ; Wed, 16 Oct 2019 16:50:33 +0300 (MSK) References: <8232b0466f3878280a9ad35cb08f437610a36486.1570539526.git.kshcherbatov@tarantool.org> <20191014164910.GA30792@tarantool.org> <20191015214734.GC898@tarantool.org> <20191016055238.GA16587@atlas> <20191016111950.GC11847@tarantool.org> From: Kirill Shcherbatov Message-ID: <6e9fe5a6-187f-29df-4b31-f00781a1a96d@tarantool.org> Date: Wed, 16 Oct 2019 16:50:32 +0300 MIME-Version: 1.0 In-Reply-To: <20191016111950.GC11847@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [tarantool-patches] Re: [PATCH v4 1/4] box: add an ability to disable CK constraints List-Id: Tarantool development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tarantool-patches@freelists.org, Nikita Pettik , tarantool-patches@dev.tarantool.org > Thanks for the scenario, now it looks reasonable. On the other hand, > if we decided to always run check constraints (both on casual and force > recovery), we would easily find out that data violates contraints. > > Kirill, could you please extend commit message with Konstantin's explanation? Done.