Re: Weird results from WHERE clause ...

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

Tried that after Rob’s earlier post Sam but it made no difference.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

> On May 12, 2016, at 4:19 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:
>
> Could this be due to decimal precision?  For example, 50.0000001 <> 50 but might compare differently in a between construct.
>
> Sam
>
> On 5/12/2016 11:53 AM, Jon Paris wrote:
> > This is running in Run SQL Scripts.
> >
> > Note my earlier comment - the ONLY difference between the working and non-working versions is that we changed the final part of the statement from:
> >
> > WHERE UniqueId BETWEEN 50 and 50;
> >
> > to
> >
> > WHERE UniqueId = 50;
> >
> > That is the ONLY change I promise.
> >
> > The first one works correctly - the second doesn’t.
> >
> > Note also that the non-working version does not fail to return a result - it just doesn’t return any values - they are all blank/null other than the UniqueId itself.
> >
> >
> > Jon Paris
> >
> > www.partner400.com
> > www.SystemiDeveloper.com
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.