Re: [Tarantool-discussions] Implicit cast for ASSIGNMENT

[Konstantin Osipov <kostja.osipov@gmail.com>]

* Mergen Imeev <imeevma@tarantool.org> [20/02/13 17:26]:

I think you suggest introducing a behaviour change between minor
releases without a proper deprecation procedure, which violates
the published release policy.

I also don't see in this email any rationale for it.

Issue 3836 is a feature and has little to do with the default
behaviour which you suggest a change. Tarantool should provide
reasonable, expected and widespread behaviour of implicit cast in
absence of CREATE CAST statement.

CREATE CAST itself is a dangerous feature which is (luckily) not
very widely used. I don't think we should do it at all.

> 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?
> 

-- 
Konstantin Osipov, Moscow, Russia