From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 80F5546971A for ; Wed, 4 Dec 2019 20:38:58 +0300 (MSK) Received: by mail-lf1-f48.google.com with SMTP id y5so220892lfy.7 for ; Wed, 04 Dec 2019 09:38:58 -0800 (PST) Date: Wed, 4 Dec 2019 20:38:55 +0300 From: Konstantin Osipov Message-ID: <20191204173855.GC19235@atlas> References: <20191124040710.d232movrzjefducx@tkn_work_nb> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191124040710.d232movrzjefducx@tkn_work_nb> Subject: Re: [Tarantool-discussions] Reusable SQL parser List-Id: Tarantool development process List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-discussions@dev.tarantool.org, Konstantin Nazarov , Nick Karlov * Alexander Turenko [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. 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? This is only a fraction of questions your proposal on this subject should address. -- Konstantin Osipov, Moscow, Russia