× 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.


  1.  Home
  2. MIDRANGE-L
  3. May 2016

Re: Weird results from WHERE clause ...

On 12-May-2016 09:05 -0500, Jon Paris wrote:
<<SNIP>>

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?

Is the UniqueId a generated value or a stored\physical value [e.g. in a primary or unique constraint key]? If generated, then how?

If not generated, then likely the change in implementation between the two queries using the different predicates [equal predicate vs BETWEEN predicate] is the origin for the issue; and presumably the query implementation of the variant producing the incorrect output would be the result of a defect to be reported to the service provider.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.