Thanks for your reply and about the query it was typo mistake.

The original question was to get an idea on the behavior change as this query was running fine with SQL...