Re: SELECT CAST(123 AS char) -> 1

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT CAST(123 AS char) -> 1
Date: 2008-02-13 15:12:29
Message-ID: 20080213151229.GB10082@crankycanuck.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jan Wieck 2008-02-13 15:15:20 Re: Deferred constraints and locks...
Previous Message Tatsuo Ishii 2008-02-13 14:48:05 Re: character conversion problem about UTF-8-->SHIFT_JIS_2004