| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | gmail Vladimir Koković <vladimir(dot)kokovic(at)gmail(dot)com> |
| Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org>, Ken Benson <Ken(at)infowerks(dot)com> |
| Subject: | Re: chr(3) and 3::text |
| Date: | 2020-03-28 15:25:52 |
| Message-ID: | CAKFQuwar77hZNwgnaCpMjOt6vAvHWnuqo-NsAgOOcqBFtzFPtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Sat, Mar 28, 2020 at 8:09 AM gmail Vladimir Koković <
vladimir(dot)kokovic(at)gmail(dot)com> wrote:
> David,
>
> Sorry for copy/paste error:replace(Filler,3::text,'') WRONG !
>
> Character 0x03 is valid in ASCII and UTF-8 character sets.
>
> Main question is, why is 3::text == '3' ?
>
The convention here is to bottom or inline post, trimming unnecessary
content.
Its that way because :: is defined to make it that way.
3 has a type of integer
'3' has a type of text
::<type> is the PostgreSQL type casting operator that casts its left to to
<type> (see the documentation I linked to)
So:
integer::text == text
cast(integer as text) == text
is the SQL Standard equivalent expression
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gmail Vladimir Koković | 2020-03-28 15:39:51 | Re: chr(3) and 3::text |
| Previous Message | gmail Vladimir Koković | 2020-03-28 15:09:47 | Re: chr(3) and 3::text |