N1QL weird behavior

n1ql
#1

I’m using the 4.5-DP and I got weird behavior when using the couchmusic1 sample data.

When running the following N1QL query:
SELECT *
FROM couchmusic1.userprofile
LIMIT 1;

I don’t get any result. However, if I execute this, I get the expected result:
SELECT *
FROM couchmusic1.userprofile
WHERE 1=1
LIMIT 1;

#2

Hi @zeus,

We are aware of this problem. We will deprecate the use of paths in the FROM clause. The problem is that couchmusic1.userprofile evaluates to MISSING in some documents, and when you apply LIMIT 1, you are getting a first document where userprofile is MISSING. The results are confusing.