Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jIBfs-0001JP-56 for pgsql-novice@arkaria.postgresql.org; Sat, 28 Mar 2020 13:38:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jIBfq-0007lW-J9 for pgsql-novice@arkaria.postgresql.org; Sat, 28 Mar 2020 13:38:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jIBfq-0007lP-8N for pgsql-novice@lists.postgresql.org; Sat, 28 Mar 2020 13:38:54 +0000 Received: from mail-wr1-x434.google.com ([2a00:1450:4864:20::434]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jIBfo-0007pk-LN for pgsql-novice@postgresql.org; Sat, 28 Mar 2020 13:38:53 +0000 Received: by mail-wr1-x434.google.com with SMTP id 65so15180554wrl.1 for ; Sat, 28 Mar 2020 06:38:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=3db/rvXRzmm9zsM4srmCyi90wfOhSrreFWFAFhMwXPo=; b=a7vR6fHI1itnleeiZF+jP/iyVBw1EeWSzV6C1Fi+oDVo+/M1M69exYyQCv2eUIFOS6 fmL9r0KeRQKiRgoXc6Lmw+djEQ/JgalbB0DzBuivoXzSZP9qniAcY7J4fFMsgavqvby7 i8TwYN3V5cLEIJYcsiI1wtlOi5sQvlIMy/tLJNkch6gsri7IoF6UNshd3eosMZXN6U8X zaWJsp1Y++JABYmbFbwb0JCddzviyNxho5coqGNsPgtC628i8qTpdMCyDEdGYepJSC3o mOOMsp+YpDGkDB3YeemAvVgjgu3rMDm1Ur9OaOQe1d3ELUCZAw6q/E2W0sdPmAx6HM3Z 4rXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=3db/rvXRzmm9zsM4srmCyi90wfOhSrreFWFAFhMwXPo=; b=M2SR1LjgxHMj6NotDgB+vKPkZ5W85ZfnaLIbJ0bPEgYg9IXw0ueMuxPkZ3R9VIe0uj TqSPJlFz6TZBNhnEHoSJWY+/qW5WXvAd9LrsnQ9UKb/Ab6pPeONiEYZGdykJdfCK2dZF 9AA1rY/s7M0O8o+s0pgDef4qYrSYvwnhq/zTFAjjVVwqHN0AdNd0RuaCSaFMK6U8gsEV 8Z9XUX+0lH/cS1/HVVHndfFxW1Rf9ihINgwZeROhD7wyFStGTgICiND5+JTDw0/Tziyv 4/31OgVhaeCvy1r2HiRbE7qP4BxTKuTdORogQaVwEOZiXIW1w00o1hN5z6OblHZ+krz2 S7nQ== X-Gm-Message-State: ANhLgQ2eGReSheoOPMtncdlgC4QGnInkzDEEjX54iq6mT+aUdpFl6PWV FhONf0YgQgBW8lna3EVEGFMQM+kvLlk= X-Google-Smtp-Source: ADFU+vvIIaOidWE5VkTdF1K1TBUZyn4TwB/yv4BQe74J2vZ8ULr4VilLd7RM6GcGrQwrYmwtKZ/Eag== X-Received: by 2002:adf:b35e:: with SMTP id k30mr4850748wrd.362.1585402729836; Sat, 28 Mar 2020 06:38:49 -0700 (PDT) Received: from [192.168.0.10] ([95.180.105.228]) by smtp.gmail.com with ESMTPSA id a64sm12255006wmh.39.2020.03.28.06.38.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Mar 2020 06:38:49 -0700 (PDT) Subject: Re: chr(3) and 3::text To: Ken Benson , "pgsql-novice@postgresql.org" References: <769c6f0f-62e1-bd7d-b3bc-221619ab4680@gmail.com> From: =?UTF-8?Q?gmail_Vladimir_Kokovi=c4=87?= Message-ID: Date: Sat, 28 Mar 2020 14:38:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------CB58D5E2876F534B8E10B7D5" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------CB58D5E2876F534B8E10B7D5 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit OK, And what is 3::text ? On 28.3.20. 14:35, Ken Benson wrote: > > *From:* gmail Vladimir Koković > *Sent:* Saturday, March 28, 2020 6:22 AM > *To:* pgsql-novice@postgresql.org > *Subject:* chr(3) and 3::text > > Hi, > > Why is chr(3) is different than 3::text ? > > */[Ken Benson] Chr(3) – means return the character that has the ASCII > code of “3” – which is a control character./* > > https://w3resource.com/PostgreSQL/chr-function.php*//* > > Examples: > > replace(Filler,chr(3),'') WORKS > > replace(Filler3::text,'') WRONG > > Vladimir Kokovic, DP senior (69) > Serbia, Belgrade, March 28, 2020 > > > > Ken Benson | ken @ infowerks-dot-com > --------------CB58D5E2876F534B8E10B7D5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

OK,


And what is 3::text ?


On 28.3.20. 14:35, Ken Benson wrote:

 

From: gmail Vladimir Koković <vladimir.kokovic@gmail.com>
Sent: Saturday, March 28, 2020 6:22 AM
To: pgsql-novice@postgresql.org
Subject: chr(3) and 3::text

 

Hi,

Why is chr(3) is different than 3::text ?

 

[Ken Benson] Chr(3) – means return the character that has the ASCII code of “3” – which is a control character.

https://w3resource.com/PostgreSQL/chr-function.php

Examples:

replace(Filler,chr(3),'') WORKS

replace(Filler3::text,'') WRONG

Vladimir Kokovic, DP senior (69)
Serbia, Belgrade, March 28, 2020



 

 

Ken Benson | ken @ infowerks-dot-com

 

 

--------------CB58D5E2876F534B8E10B7D5--