From: Konstantin Osipov <kostja@tarantool.org>
To: "Никита Петтик" <kitnerh@gmail.com>
Cc: tarantool-patches@freelists.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 2/3] Add surrogate ID for BINARY collation
Date: Thu, 1 Nov 2018 23:06:10 +0300 [thread overview]
Message-ID: <20181101200610.GB5887@chai> (raw)
In-Reply-To: <20181101200027.GA5887@chai>
My point is - in future you may want an object with some kind of
context to represent binary and absent collation. Right now an id
is sufficient in all contexts, but in future it may be easier to
treat all collations the same way.
For example, collation "weight" in comparisons could be
represent as an integer number. As long as you don't have an
object for binary and "none" collations, you will have to treat
them in a special way, while you could simply compare their
strength with each other. The same is about collation name - you
may need to print collation name in an error message. If "none"
and "binary" are only ids, you will, once again, have to treat
them separately.
* Konstantin Osipov <kostja@tarantool.org> [18/11/01 23:00]:
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2018-11-01 20:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 11:00 [tarantool-patches] [PATCH 0/3] Change collation compatibility rules according to ANSI SQL Nikita Pettik
2018-10-25 11:00 ` [tarantool-patches] [PATCH 1/3] sql: do not add explicit <COLLATE "BINARY"> clause Nikita Pettik
2018-10-25 11:00 ` [tarantool-patches] [PATCH 2/3] Add surrogate ID for BINARY collation Nikita Pettik
2018-10-31 12:34 ` [tarantool-patches] " Vladislav Shpilevoy
2018-10-31 15:47 ` n.pettik
2018-11-01 11:37 ` Konstantin Osipov
2018-11-01 12:22 ` Vladislav Shpilevoy
2018-11-01 12:58 ` Konstantin Osipov
2018-11-01 13:08 ` n.pettik
2018-11-01 15:39 ` Konstantin Osipov
[not found] ` <95CB17D5-E3ED-4B05-A289-983E2FD0DE37@gmail.com>
2018-11-01 17:45 ` n.pettik
2018-11-01 20:00 ` Konstantin Osipov
2018-11-01 20:06 ` Konstantin Osipov [this message]
2018-11-01 20:20 ` n.pettik
2018-10-25 11:00 ` [tarantool-patches] [PATCH 3/3] sql: change collation compatibility rules Nikita Pettik
2018-10-31 12:34 ` [tarantool-patches] " Vladislav Shpilevoy
2018-11-12 23:46 ` n.pettik
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=20181101200610.GB5887@chai \
--to=kostja@tarantool.org \
--cc=kitnerh@gmail.com \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH 2/3] Add surrogate ID for BINARY collation' \
/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