×
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.
I get SQLSTATE 01565.
-----Original Message-----
From: John Yeung [mailto:gallium.arsenide@xxxxxxxxx]
Sent: Thursday, February 27, 2020 10:33 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Compatible data types in SQL CASE expressions
The SQL Reference has this to say about result expressions within CASE
expressions:
All result-expressions must have compatible data types
It doesn't tell you the consequences of not satisfying this requirement, but I would have guessed that you get some kind of error message.
And I would have been wrong.
Apparently, what can happen if you have two conflicting data types in two branches of a CASE expression is that one of them "wins" and the other becomes NULL. Without generating any error message.
Lesson learned. Until I forget it again. :P
John Y.
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.
midrange.com
