From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alexander.turenko@tarantool.org>
Received: from smtp58.i.mail.ru (smtp58.i.mail.ru [217.69.128.38])
 (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 A5B8D46971A
 for <tarantool-discussions@dev.tarantool.org>;
 Thu, 12 Dec 2019 04:21:38 +0300 (MSK)
Date: Thu, 12 Dec 2019 04:21:32 +0300
From: Alexander Turenko <alexander.turenko@tarantool.org>
Message-ID: <20191212012132.iiy2ww4qxcjftpk2@tkn_work_nb>
References: <20191124040710.d232movrzjefducx@tkn_work_nb>
 <20191204173855.GC19235@atlas>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191204173855.GC19235@atlas>
Subject: Re: [Tarantool-discussions] Reusable SQL parser
List-Id: Tarantool development process
 <tarantool-discussions.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-discussions>, 
 <mailto:tarantool-discussions-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-discussions/>
List-Post: <mailto:tarantool-discussions@dev.tarantool.org>
List-Help: <mailto:tarantool-discussions-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-discussions>, 
 <mailto:tarantool-discussions-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>
Cc: tarantool-discussions@dev.tarantool.org, Konstantin Nazarov <racktear@tarantool.org>, Nick Karlov <karlovn@tarantool.org>

On Wed, Dec 04, 2019 at 08:38:55PM +0300, Konstantin Osipov wrote:
> * Alexander Turenko <alexander.turenko@tarantool.org> [19/11/24 10:13]:
> > Discussions about ways to reuse Tarantool SQL parser in applications and
> > connectors arise from time to time. I want to share a very high-level proposal
> > how we can reuse the parser in an application and provide some examples we
> > heard from users.
> 
> I think this proposal as formulated here is a no-brainer.

Sure.

I wrote this (and other) proposals here in order to share motivation
under features we intend to implement: what exactly we asked for or what
do we want to achieve. So it is more about 'why', then 'how'.

Usually it is squeezing from one or several meetings.

My intention here is to have a linkable (and so public) statements about
motivation under our work, especially when it is relatively big.

Maybe you may suggest better wording for such statements.

> The question is how best to do it. Shall we try to be ABI
> compatible? How to version the ABI? How to operate heterogenous
> clusters and clusters during an upgrade?

Yep.

> This is only a fraction of questions your proposal on this subject
> should address.

Don't mind to share your thoughts on this. I would appreciate it.

WBR, Alexander Turenko.