From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <korablev@tarantool.org>
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 6A7BA41D0BD
 for <tarantool-patches@dev.tarantool.org>;
 Wed, 16 Oct 2019 21:09:14 +0300 (MSK)
Date: Wed, 16 Oct 2019 21:09:13 +0300
From: Nikita Pettik <korablev@tarantool.org>
Message-ID: <20191016180913.GB23167@tarantool.org>
References: <cover.1570539526.git.kshcherbatov@tarantool.org>
 <8232b0466f3878280a9ad35cb08f437610a36486.1570539526.git.kshcherbatov@tarantool.org>
 <20191014164910.GA30792@tarantool.org>
 <f30e882a-e710-25e1-71c1-79dca24a61bc@tarantool.org>
 <20191015214734.GC898@tarantool.org> <20191016055238.GA16587@atlas>
 <20191016111950.GC11847@tarantool.org>
 <6e9fe5a6-187f-29df-4b31-f00781a1a96d@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <6e9fe5a6-187f-29df-4b31-f00781a1a96d@tarantool.org>
Subject: Re: [Tarantool-patches] [tarantool-patches] Re: [PATCH v4 1/4] box:
 add an ability to disable CK constraints
List-Id: Tarantool development <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Kirill Shcherbatov <kshcherbatov@tarantool.org>
Cc: tarantool-patches@freelists.org, tarantool-patches@dev.tarantool.org

On 16 Oct 16:50, Kirill Shcherbatov wrote:
> > 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.

Pushed to master.