From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng2.m.smailru.net (smtpng2.m.smailru.net [94.100.179.3]) (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 41D68469719 for ; Tue, 3 Mar 2020 13:15:59 +0300 (MSK) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\)) From: Roman Khabibov In-Reply-To: <333643e7-dbc5-7cce-6485-f0d4ae60cda8@tarantool.org> Date: Tue, 3 Mar 2020 13:15:58 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <8E61BD87-D152-4569-B18F-992005BD66A7@tarantool.org> References: <20200229124645.67971-1-roman.habibov@tarantool.org> <20200229124645.67971-2-roman.habibov@tarantool.org> <333643e7-dbc5-7cce-6485-f0d4ae60cda8@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v2 1/3] sql: improve "no such constraint" error message List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org > On Feb 29, 2020, at 18:31, Vladislav Shpilevoy = wrote: >=20 >=20 >=20 > On 29/02/2020 13:46, Roman Khabibov wrote: >> Clarify the error message for better user handling. Add the name >> of space where the constraint under dropping didn't founded. >=20 > didn't -> wasn=E2=80=99t Fixed.=