From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
tarantool-discussions@dev.tarantool.org,
Peter Gulutzan <pgulutzan@ocelot.ca>,
georgy@tarantool.org
Subject: Re: [Tarantool-discussions] [Tarantool-patches] [PATCH v3 0/5] Replace control pragmas by SET
Date: Wed, 18 Dec 2019 13:53:53 +0300 [thread overview]
Message-ID: <20191218105352.7mk7f655ep7hkyp4@tkn_work_nb> (raw)
In-Reply-To: <20191218102051.qgfa6nskqgrsqh4j@tarantool.org>
> To sum up. We spent too much time here. I think we can improve approaches
> in future. But I see no serious reasons for that:
> 1. To make it easier to use we might whant to implement some stored
> routines or something/
> 2. Performance of encode/decode is out of intereset here.
>
> I propose you to file a feature request as follow up of the patchset.
I read this as 'any design / API is okay'. So there is no sense to
discuss it further.
For me access a field of a structure with msgpack encode and then decode
is a kind of `toString(bool_value).length() != 5` check.
It is a bit toxic, I know. Sorry for this.
WBR, Alexander Turenko.
prev parent reply other threads:[~2019-12-18 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1573121685.git.imeevma@gmail.com>
[not found] ` <20191206113711.ctzr6x7sqbpr3xkd@tarantool.org>
2019-12-06 13:50 ` Mergen Imeev
2019-12-06 14:06 ` Sergey Ostanevich
2019-12-17 22:11 ` Alexander Turenko
2019-12-18 2:39 ` Peter Gulutzan
2019-12-18 17:39 ` Peter Gulutzan
2019-12-19 9:59 ` Mergen Imeev
2019-12-19 17:35 ` Peter Gulutzan
2019-12-19 17:51 ` Mergen Imeev
2019-12-19 21:09 ` Vladislav Shpilevoy
2019-12-18 10:20 ` Kirill Yukhin
2019-12-18 10:53 ` Alexander Turenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191218105352.7mk7f655ep7hkyp4@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=georgy@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=pgulutzan@ocelot.ca \
--cc=tarantool-discussions@dev.tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-discussions] [Tarantool-patches] [PATCH v3 0/5] Replace control pragmas by SET' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox