Re: SELECT CAST(123 AS char) -> 1 - Mailing list pgsql-general

From Tom Lane
Subject Re: SELECT CAST(123 AS char) -> 1
Date
Msg-id 20058.1203178531@sss.pgh.pa.us
Whole thread Raw
In response to Re: SELECT CAST(123 AS char) -> 1  (Ken Johanson <pg-user@kensystem.com>)
List pgsql-general
Ken Johanson <pg-user@kensystem.com> writes:
> Tom Lane wrote:
>> Hm, good point, so really we ought to have a separate casting path for
>> numeric types to char(n).  However, this section still doesn't offer
>> any support for the OP's desire to auto-size the result; it says
>> that you get an error if the result doesn't fit in the declared
>> length:
>>
>>> iv) Otherwise, an exception condition is raised: data exception-
>>> string data, right truncation.

> I don't believe the size is being declared in the OP's (subject line)
> example:  SELECT CAST(123 AS char)

No, because section 6.1 still defines what "char" means, and it says
that means "char(1)".

            regards, tom lane

pgsql-general by date:

Previous
From: "Phoenix Kiula"
Date:
Subject: Re: Timestamp indexes (why ">" or "between" does not use index?)
Next
From: Ken Johanson
Date:
Subject: Re: Strict-typing benefits/costs