From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Nikita Pettik <korablev@tarantool.org>
Cc: tarantool-discussions@dev.tarantool.org
Subject: Re: [Tarantool-discussions] Implicit cast for COMPARISON
Date: Fri, 7 Feb 2020 17:40:54 +0300 [thread overview]
Message-ID: <20200207144054.GB4105@atlas> (raw)
In-Reply-To: <20200207142446.GA1110@tarantool.org>
* Nikita Pettik <korablev@tarantool.org> [20/02/07 17:29]:
> Alternatively, we can abandon this idea and operate apply comparison
> rules depending purely on mp_ types of particular scalar values. But
> then rules in NoSQL and SQL will be different.
This would be worst thing of all. mp_type is an encoding format,
which, btw, I would like to ditch from in-memory tuple format
going forward (only keep for data on disk and wirte) - 'cause
compression benefits it gives do not outweigh the performance
slow down of variable representation or need to pack/unpack.
There should be a single set of data types for SQL and NoSQL and
the rules should be the same. If NoSQL types don't have some ansi
features, then these features should be added to nosql, and sql
should use nosql.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-02-07 14:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 11:11 Mergen Imeev
2020-01-21 18:09 ` Peter Gulutzan
2020-01-22 14:13 ` Mergen Imeev
2020-01-22 14:24 ` Nikita Pettik
2020-01-30 18:51 ` Konstantin Osipov
2020-01-22 16:43 ` Peter Gulutzan
2020-01-30 18:52 ` Konstantin Osipov
2020-02-03 11:35 ` Mergen Imeev
2020-02-03 15:02 ` Konstantin Osipov
2020-02-04 18:50 ` Nikita Pettik
2020-02-05 2:57 ` Peter Gulutzan
2020-02-07 14:24 ` Nikita Pettik
2020-02-07 14:40 ` Konstantin Osipov [this message]
2020-02-07 22:30 ` Peter Gulutzan
2020-02-11 13:32 ` Mergen Imeev
2020-02-05 7:52 ` Mergen Imeev
2020-02-06 12:41 ` Mergen Imeev
2020-02-06 13:09 ` Mergen Imeev
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=20200207144054.GB4105@atlas \
--to=kostja.osipov@gmail.com \
--cc=korablev@tarantool.org \
--cc=tarantool-discussions@dev.tarantool.org \
--subject='Re: [Tarantool-discussions] Implicit cast for COMPARISON' \
/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