Re: Compatible data types in SQL CASE expressions -- MIDRANGE-L

Subject: Re: Compatible data types in SQL CASE expressions
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 27 Feb 2020 13:48:10 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Thu, Feb 27, 2020 at 1:04 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I get SQLSTATE 01565.

Ah, fair enough. The "messages and codes" reference says that states
starting with 01 are "just" warnings, so that would explain why the
operation still succeeds.

I'll accept that it's my responsibility to be aware of possible
warnings. I still disagree with the wording in the reference regarding
CASE expressions. To me, "must" implies a hard error is coming if you
fail to meet the requirement, unless there is an explicit explanation
otherwise.

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Compatible data types in SQL CASE expressions , Justin Taylor

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.