From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 23 Apr 2019 16:44:20 +0300 From: Konstantin Osipov Subject: Re: [tarantool-patches] Re: [PATCH] Add MsgPack ext types handling. Message-ID: <20190423134420.GB6068@chai> References: <20190423113732.20786-1-sergepetrenko@tarantool.org> <20190423122146.GA5668@chai> <39783BF9-0E1F-4AB0-B538-B7F2A2A123FF@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <39783BF9-0E1F-4AB0-B538-B7F2A2A123FF@tarantool.org> To: Serge Petrenko Cc: Vladimir Davydov , tarantool-patches@freelists.org List-ID: * Serge Petrenko [19/04/23 16:05]: > > > > 23 апр. 2019 г., в 15:21, Konstantin Osipov написал(а): > > > > * Serge Petrenko [19/04/23 15:09]: > > > > I mentioned before that this would break all clients. > > > > It's high time to reconsider our in-memory storage format and make > > it different from serialization format: we're seeing significant > > performance penalty with serialization to and from msgpack in SQL, > > and DECIMAL is a yet another blow on the single-format-approach: > > our clients are simply not prepared to handle non-standard > > extensions. > > > > Let's investigate what it takes to store decimal as an mp ext, and > > serialize as mp string. > > Well, we can do this, but how can clients distinguish decimal and string then? >From result set metadata or, more generally, from schema. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov