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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Compatible data types in SQL CASE expressions
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Fri, 28 Feb 2020 09:19:01 -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 Fri, Feb 28, 2020 at 9:04 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Personally, I treat anything but 00000 and 02000 as abnormal conditions (unless explicitly ignored).

There are contexts where warnings are not exposed, at least not
readily. Rob already mentioned Run SQL Scripts. Another is pyodbc,
through which I do almost all my SQL work. I don't know if other ODBC
wrappers provide greater exposure.

John Y.

As an Amazon Associate we earn from qualifying purchases.

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.