From: Imeev Mergen <imeevma@tarantool.org>
To: tarantool-discussions@dev.tarantool.org, kostja.osipov@gmail.com,
pgulutzan@ocelot.ca, korablev@tarantool.org,
alexander.turenko@tarantool.org, v.shpilevoy@tarantool.org,
kyukhin@tarantool.org, tsafin@tarantool.org
Subject: Re: [Tarantool-discussions] Implicit cast for ASSIGNMENT
Date: Thu, 30 Apr 2020 15:04:11 +0300 [thread overview]
Message-ID: <36e21524-35d7-9f54-5953-32863df95709@tarantool.org> (raw)
In-Reply-To: <20200213142534.GA26443@tarantool.org>
Hi! Here we go again. Last time we have not come to a colclusion.
So, I suggest these rules for implicit cast for ASSIGNMENT:
1) Any value can be implicitly cast to ANY type.
2) Any scalar values can be implicitly cast to SCALAR type.
3) Values of numeric types can be implicitly cast to other numeric
types.
4) Implicit casting is prohibited, except as described above.
I think that the rules for implicit casting when assigning value
of numeric type must be the same as in C.
On 2/13/20 5:25 PM, Mergen Imeev wrote:
> Hi all,
> I would like to discuss the second issue of casts in SQL. I mean
> implicit casting for ASSIGNMENT.
>
> For now, I suggest avoiding questions about SCALAR, as the
> discussion is already in progress.
>
> So, I suggest removing the current implicit casts. We can
> reimplement implicit casts in accordance with ANSI in issue #3836.
> But since priority of #3836 is low, this is most likely not going
> to happen for some time.
>
> At the moment, I see two ways to remove implicit casts:
> 1) Disable all implicit casts, except casts for numeric values.
> These casts will become UDCF later.
> 2) Disable all implicit casts. Assignment in Tarantool-SQL will
> work the same as in noSQL Tarantool.
>
> What do you think about this?
>
next prev parent reply other threads:[~2020-04-30 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:25 Mergen Imeev
2020-02-13 14:40 ` Konstantin Osipov
2020-02-13 22:20 ` Peter Gulutzan
2020-04-30 12:04 ` Imeev Mergen [this message]
2020-04-30 12:35 ` Konstantin Osipov
2020-04-30 12:56 ` Imeev Mergen
2020-04-30 13:09 ` Konstantin Osipov
2020-04-30 13:12 ` Imeev Mergen
2020-04-30 14:04 ` Konstantin Osipov
2020-04-30 14:15 ` Peter Gulutzan
2020-04-30 14:28 ` Konstantin Osipov
2020-04-30 14:40 ` Peter Gulutzan
2020-04-30 15:10 ` Imeev Mergen
2020-04-30 16:04 ` Peter Gulutzan
2020-05-07 16:14 ` Peter Gulutzan
2020-05-08 11:57 ` Kirill Yukhin
2020-04-30 22:52 ` [Tarantool-discussions] Descriptive SQL Style Guide Peter Gulutzan
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=36e21524-35d7-9f54-5953-32863df95709@tarantool.org \
--to=imeevma@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=korablev@tarantool.org \
--cc=kostja.osipov@gmail.com \
--cc=kyukhin@tarantool.org \
--cc=pgulutzan@ocelot.ca \
--cc=tarantool-discussions@dev.tarantool.org \
--cc=tsafin@tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-discussions] Implicit cast for ASSIGNMENT' \
/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