From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 4882030AB9 for ; Fri, 21 Jun 2019 08:11:49 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGfRVcfO23a0 for ; Fri, 21 Jun 2019 08:11:49 -0400 (EDT) Received: from smtp29.i.mail.ru (smtp29.i.mail.ru [94.100.177.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id A719D30A67 for ; Fri, 21 Jun 2019 08:11:48 -0400 (EDT) Date: Fri, 21 Jun 2019 15:11:44 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [RFC] box/lua/console: Add console.fmt module Message-ID: <20190621121144.GA5998@atlas> References: <20190620215405.9338-1-gorcunov@gmail.com> <20190621073241.GJ18958@atlas> <20190621073643.GK18958@atlas> <20190621080918.GA18551@uranus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190621080918.GA18551@uranus> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Cyrill Gorcunov Cc: tarantool-patches@freelists.org, Alexander Turenko * Cyrill Gorcunov [19/06/21 11:10]: > On Fri, Jun 21, 2019 at 10:36:43AM +0300, Konstantin Osipov wrote: > > * Konstantin Osipov [19/06/21 10:32]: > > > > Last thing: Lua output should become the default. > > But it will break backward compatibility, is it ok? Yes, it's OK for 2.x series. > > It should perhaps also be possible to set the output > > format of every console individually. > > OK, i think it should be a next step. At the moment I'm > gathering feedback to make code flexible enough for > extensions. > > Previously you pointed that we might need to support > json/sql formats and such. Could you please elaborate > with some examples so I would treat them as a vectore > where to move in general design. For JSON, please take a look at how MongoDB presents its output. For SQL, PostgreSQL or MySQL or CockroachDB would be nice -they even colorize table headings. In any case, SQL demands tabular form. Tabular output is difficult. Especially with non-ascii characters and alphabets, which have digraphs, and ligatures. -- Konstantin Osipov, Moscow, Russia