From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 5B619469719 for ; Thu, 13 Feb 2020 17:40:03 +0300 (MSK) Received: by mail-lf1-f49.google.com with SMTP id b15so4444801lfc.4 for ; Thu, 13 Feb 2020 06:40:03 -0800 (PST) Date: Thu, 13 Feb 2020 17:40:00 +0300 From: Konstantin Osipov Message-ID: <20200213144000.GA32013@atlas> References: <20200213142534.GA26443@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200213142534.GA26443@tarantool.org> Subject: Re: [Tarantool-discussions] Implicit cast for ASSIGNMENT List-Id: Tarantool development process List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mergen Imeev Cc: tarantool-discussions@dev.tarantool.org * Mergen Imeev [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