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

From Andrew Sullivan
Subject Re: SELECT CAST(123 AS char) -> 1
Date
Msg-id 20080213151229.GB10082@crankycanuck.ca
Whole thread Raw
In response to Re: SELECT CAST(123 AS char) -> 1  (Ken Johanson <pg-user@kensystem.com>)
Responses Re: SELECT CAST(123 AS char) -> 1
List pgsql-general
On Tue, Feb 12, 2008 at 08:39:05PM -0700, Ken Johanson wrote:

> between 3rd party products (customer API and database x^n). I'm trying
> to convey here that changing the behavior to a (numb AS varchar) one,
> practically speaking, is more benign/useful (vs now), even if that is
> only a non-spec workaround, and "everyone else does it" is an invalid
> arg.

No, you're trying to convey that it is more benign/useful _to you_.  Others
are arguing that they want to write conformant code, and don't much care
what MyOccasionallyReadTheSpec does.  It's a pity that SQL conformance is
not better across systems, but surely the way to improve that is to reduce
the number of products that are being careless, not to increase them?

A


pgsql-general by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: character conversion problem about UTF-8-->SHIFT_JIS_2004
Next
From: Peter Wilson
Date:
Subject: Re: Storing images as BYTEA or large objects