| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Ken Johanson <pg-user(at)kensystem(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SELECT CAST(123 AS char) -> 1 |
| Date: | 2008-02-13 16:56:47 |
| Message-ID: | 20080213165647.GG11314@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ken Johanson wrote:
> Alvaro Herrera wrote:
>> If you are arguing that the spec's definition of the CHARACTER type is
>> not really very useful, I think you are going to find a lot of
>> supporters. You can send your complaints to the SQL committee; but
>> then, it is unlikely that this is going to change anytime soon because
>> of the fear of breaking backwards compatibility.
>
> Agreed. There may be allot of users who in the case of CAST, need to
> extract the leftmost digit, and for those database and their users that
> do this by default, it would cause harm.
Right. And those that don't need that are certainly using a cast to
CHARACTER VARYING.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2008-02-13 17:53:42 | Re: SELECT CAST(123 AS char) -> 1 |
| Previous Message | Ken Johanson | 2008-02-13 16:29:41 | Re: SELECT CAST(123 AS char) -> 1 |