From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp61.i.mail.ru (smtp61.i.mail.ru [217.69.128.41]) (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 559B146970E for ; Fri, 27 Dec 2019 20:07:25 +0300 (MSK) Date: Fri, 27 Dec 2019 19:07:23 +0200 From: Nikita Pettik Message-ID: <20191227170723.GL18639@tarantool.org> References: <0c1ac93e3969350e6a455dbf50bacab87daf5f8b.1576074906.git.korablev@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0c1ac93e3969350e6a455dbf50bacab87daf5f8b.1576074906.git.korablev@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] sql: display line and position in syntax errors List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tarantool-patches@dev.tarantool.org On 11 Dec 17:36, Nikita Pettik wrote: > When it comes for huge queries, it may turn out to be useful to see > exact position of occurred error. Hence, let's now display line and > position within line near which syntax error takes place. Note that it > can be done only during parsing process (since AST can be analysed only > after its construction is completed), so most of semantic errors still > don't contain position. A few errors have been reworked to match new > formatting patterns. > > First iteration of this patch is implemented by @romanhabibov > > Closes #2611 > --- > Branch: https://github.com/tarantool/tarantool/tree/np/gh-2611-line-pos-syntax-error > Issue: https://github.com/tarantool/tarantool/issues/2611 > v1: https://lists.tarantool.org/pipermail/tarantool-patches/2019-October/011841.html If nobody has objections (concerning new error messages patterns), I am going to push it.