Re: String literal doesn't autocast to text type - Mailing list pgsql-general

From Alex Ignatov
Subject Re: String literal doesn't autocast to text type
Date
Msg-id 06D13A01-78AE-42B3-BB11-0EEAE89F0A80@postgrespro.ru
Whole thread Raw
In response to Re: String literal doesn't autocast to text type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

> On 04 Mar 2016, at 21:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Alex Ignatov <a.ignatov@postgrespro.ru> writes:
>> Why string literal like 'Hello world!' doesnt automagicaly cast to text
>> type?
>
> Because it's not necessarily a string.  It might be meant to be point,
> or json, or any number of other types.
>
>> Sure we can create our cast:
>> postgres=# create cast (unknown as text) with inout as implicit;
>> CREATE CAST
>
> That's a seriously bad idea; it will have all sorts of corner-case
> effects that you aren't expecting.
>
> There has been some talk of forcing unknown to text in the output
> columns of a sub-SELECT, which would fix the example you show with
> a lot less risk of side-effects elsewhere.  But it's not exactly
> trivial because of interactions with INSERT ... SELECT.
>
>            regards, tom lane
Oh! Thank you , Tom!


pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: String literal doesn't autocast to text type
Next
From: "David G. Johnston"
Date:
Subject: Re: multiple UNIQUE indices for FK