From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 3/5] sql: use 'varbinary' as a name of type instead of 'blob'
Date: Tue, 30 Jul 2019 16:43:06 +0300 [thread overview]
Message-ID: <93CF3B4E-A159-491A-8253-F3F5D9FBF875@tarantool.org> (raw)
In-Reply-To: <027525d2-deed-d70b-b06b-3e49bf92d7c3@tarantool.org>
>>> func.c :540, :1185, :1254, :1753
>>> vdbeapi.c:283, :382, :1061
>>> vdbemem.c:996, :1022
>>> vdbeaux.c:1192
>>
>> All these usages are in form of:
>> "string or blob is too big”
>>
>> I think that blob is a good name for entity of varbinary
>> type. Another possible names are “binary sequence”,
>> “binary data” or “binary string”. The latter variant is used
>> in the ANSI specification. Now I’ve changed to “binary string”,
>> but if you can suggest better name, let’s discuss it.
>
> No, I don't mind any name. I saw, that in the commit message
> you said
>
> "Thus, let's fix all visible to user messages using 'varbinary'
> name of type instead of 'blob'."
>
> And I noticed, that there are still visible messages mentioning blob.
> You can keep blob, or rename, or anything.
I’m okay with "binary string” as well, so let’s keep it.
next prev parent reply other threads:[~2019-07-30 13:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 11:42 [tarantool-patches] [PATCH 0/5] Introduce VARBINARY in SQL Nikita Pettik
2019-07-24 11:42 ` [tarantool-patches] [PATCH 1/5] sql: always erase numeric flag after stringifying Nikita Pettik
2019-07-24 11:42 ` [tarantool-patches] [PATCH 2/5] sql: fix resulting type calculation for CASE-WHEN stmt Nikita Pettik
2019-07-25 22:12 ` [tarantool-patches] " Vladislav Shpilevoy
[not found] ` <a061e845-eeb1-00d1-9141-3b9bb87768f5@tarantool.org>
2019-07-28 23:56 ` n.pettik
2019-07-24 11:42 ` [tarantool-patches] [PATCH 3/5] sql: use 'varbinary' as a name of type instead of 'blob' Nikita Pettik
2019-07-25 22:11 ` [tarantool-patches] " Vladislav Shpilevoy
[not found] ` <2e655514-0fec-8baf-20a8-d49e5586b047@tarantool.org>
2019-07-28 23:56 ` n.pettik
2019-07-29 21:03 ` Vladislav Shpilevoy
2019-07-30 13:43 ` n.pettik [this message]
2019-07-24 11:42 ` [tarantool-patches] [PATCH 4/5] sql: make built-ins raise errors for varbin args Nikita Pettik
2019-07-25 22:11 ` [tarantool-patches] " Vladislav Shpilevoy
[not found] ` <05d15035-2552-1f05-b7ce-facfbbc3a520@tarantool.org>
2019-07-28 23:59 ` n.pettik
2019-07-24 11:42 ` [tarantool-patches] [PATCH 5/5] sql: introduce VARBINARY column type Nikita Pettik
2019-07-25 22:12 ` [tarantool-patches] " Vladislav Shpilevoy
[not found] ` <49a188eb-dafe-44e7-a0fd-e9244b68e721@tarantool.org>
2019-07-29 0:03 ` n.pettik
2019-07-29 20:55 ` Vladislav Shpilevoy
2019-07-30 13:44 ` n.pettik
2019-07-30 19:41 ` Vladislav Shpilevoy
2019-07-30 19:52 ` Vladislav Shpilevoy
2019-07-31 14:51 ` n.pettik
2019-08-01 8:42 ` [tarantool-patches] Re: [PATCH 0/5] Introduce VARBINARY in SQL Kirill Yukhin
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=93CF3B4E-A159-491A-8253-F3F5D9FBF875@tarantool.org \
--to=korablev@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH 3/5] sql: use '\''varbinary'\'' as a name of type instead of '\''blob'\''' \
/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