From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [87.239.111.99] (localhost [127.0.0.1]) by dev.tarantool.org (Postfix) with ESMTP id B3C946EC40; Fri, 13 Aug 2021 01:23:56 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org B3C946EC40 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tarantool.org; s=dev; t=1628807036; bh=cwyzK4kSOZadH8lBGdx0exjtNnQD4FXQMzbxm1Ctll0=; h=Date:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=oiy6CHed2Ny259O/m0d2lrM9N4ntCNMovfZDYNvgBEZT450T0a80cTSJjnPWoOXHR epB/Mq8aJBSsHkYCgSFZD4rXhNwXzM64aakcCvMm15010fNeoppm/BZkPv3ku1tm15 S2g7j8adNzcihq8F+yKEQkhXffjv8Fydp2SqcRF0= Received: from smtpng2.i.mail.ru (smtpng2.i.mail.ru [94.100.179.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id BC3F46EC40 for ; Fri, 13 Aug 2021 01:23:54 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 dev.tarantool.org BC3F46EC40 Received: by smtpng2.m.smailru.net with esmtpa (envelope-from ) id 1mEJ7C-0008Ip-3z; Fri, 13 Aug 2021 01:23:54 +0300 Date: Fri, 13 Aug 2021 01:23:52 +0300 To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org Message-ID: <20210812222352.GA206429@tarantool.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-4EC0790: 10 X-7564579A: 646B95376F6C166E X-77F55803: 4F1203BC0FB41BD92087353F0EC44DD972FF4A7D76DB5E242D14FEF1BD8BF4AC182A05F5380850405D2AD5725A67EF3A742EAD4459756B0F4BE971105B0C22BF6FC11C702AB263A4 X-7FA49CB5: FF5795518A3D127A4AD6D5ED66289B5278DA827A17800CE7A3DED2DACB82E709C2099A533E45F2D0395957E7521B51C2CFCAF695D4D8E9FCEA1F7E6F0F101C6778DA827A17800CE7EC0B1A4921CAE631EA1F7E6F0F101C6723150C8DA25C47586E58E00D9D99D84E1BDDB23E98D2D38BBCA57AF85F7723F213C1BC8FEC8A08B6C6261368B2053CDCCC7F00164DA146DAFE8445B8C89999728AA50765F7900637712AAB6D9D366D8A389733CBF5DBD5E9C8A9BA7A39EFB766F5D81C698A659EA7CC7F00164DA146DA9985D098DBDEAEC8093C2F12201C912AF6B57BC7E6449061A352F6E88A58FB86F5D81C698A659EA7E827F84554CEF5019E625A9149C048EE9ECD01F8117BC8BEE2021AF6380DFAD18AA50765F790063735872C767BF85DA227C277FBC8AE2E8BDC0F6C5B2EEF3D0C75ECD9A6C639B01B4E70A05D1297E1BBCB5012B2E24CD356 X-B7AD71C0: AC4F5C86D027EB782CDD5689AFBDA7A213B5FB47DCBC3458834459D11680B50551B1FFFA53AFF59FA7101511D9EDDDA8 X-C1DE0DAB: 0D63561A33F958A5F7B9523DC28889702391277F5FED8BBE325B5BACEAA8B8C5D59269BC5F550898D99A6476B3ADF6B47008B74DF8BB9EF7333BD3B22AA88B938A852937E12ACA75907D60A27468CB01410CA545F18667F91A7EA1CDA0B5A7A0 X-C8649E89: 4E36BF7865823D7055A7F0CF078B5EC49A30900B95165D34B5900AD87B4159A4B25E326E4C2DC632BA5C8ECF7224864DEACEDC1327010CABDAD6B3F101D663501D7E09C32AA3244CF4DB4DEA9AECDEA4F792566730EBCA278580396430872480729B2BEF169E0186 X-D57D3AED: 3ZO7eAau8CL7WIMRKs4sN3D3tLDjz0dLbV79QFUyzQ2Ujvy7cMT6pYYqY16iZVKkSc3dCLJ7zSJH7+u4VD18S7Vl4ZUrpaVfd2+vE6kuoey4m4VkSEu530nj6fImhcD4MUrOEAnl0W826KZ9Q+tr5ycPtXkTV4k65bRjmOUUP8cvGozZ33TWg5HZplvhhXbhDGzqmQDTd6OAevLeAnq3Ra9uf7zvY2zzsIhlcp/Y7m53TZgf2aB4JOg4gkr2bioj0dLV0c3jbkwq6DUWGCpoVQ== X-Mailru-Sender: 689FA8AB762F7393C37E3C1AEC41BA5DAA476BCB218A873FCB11DBECCD05424D83D72C36FC87018B9F80AB2734326CD2FB559BB5D741EB96352A0ABBE4FDA4210A04DAD6CC59E33667EA787935ED9F1B X-Mras: Ok Subject: Re: [Tarantool-patches] [PATCH v1 7/7] sql: fix comparison with SCALAR value X-BeenThere: tarantool-patches@dev.tarantool.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Mergen Imeev via Tarantool-patches Reply-To: Mergen Imeev Errors-To: tarantool-patches-bounces@dev.tarantool.org Sender: "Tarantool-patches" On Thu, Aug 12, 2021 at 09:50:35PM +0300, Vladislav Shpilevoy wrote: > Thanks for the patch! > > On 11.08.2021 19:01, Mergen Imeev via Tarantool-patches wrote: > > After this patch, SCALAR values will be able to be compared with values > > of any other scalar type. The comparison will be done according to the > > SCALAR rules, which means boolean values < numeric values < string > > values < binary values < uuid values. > > > > Closes #6221 > > Could you please add a docbot request? Fixed: commit 6179b16e422a1349ebe5b0ed340c81d8f5a4e6a2 Author: Mergen Imeev Date: Wed Aug 11 14:58:23 2021 +0300 sql: fix comparison with SCALAR value After this patch, SCALAR values will be able to be compared with values of any other scalar type. The comparison will be done according to the SCALAR rules, which means boolean values < numeric values < string values < binary values < uuid values. Closes #6221 @TarantoolBot document Title: SCALAR and NUMBER values in SQL SCALAR values can now be compared with values of any other scalar type, but cannot be implicitly cast to any other scalar type. This means that SCALAR values cannot participate in arithmetic, bitwise operations, concatenation, or functions that, by definition, do not accept SCALAR values. NUMBER values now also cannot be implicitly cast to any other numeric type, which means that NUMBER values cannot participate in arithmetic and bitwise operations, or in functions that, by definition, do not accept NUMBER values.