×
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.
OK SQL gurus - need your help here. I’m pretty sure this has to be an SQL bug but if so I’d have expected it to have been reported before now and I can’t find anything on IBM’s site that sounds similar.
Have a large complex CTE which produces a weird result if I use = in the WHERE compared with BETWEEN.
For example SELECT * from MyCTE where UniqueId between 50 and 50 produces the expected single row result with all columns correctly populated.
On the other hand SELECT * from MyCTE where UniqueId = 50 also produces a single row but all columns are empty/null. Needless to say the results should be identical.
Originally this was run on a 6.1 system so it was moved to a pretty current 7.1 box with identical results.
Anyone seen this or anything like it?
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
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
