Using whole document as query doesn't return the document in some cases
9 views
Skip to first unread message
Mirza Kapetanovic
May 30, 2014, 7:32:07 AM5/30/14
to node-mong...@googlegroups.com
I've encountered some strange behaviour when using a whole document as query with collection.find. There are some documents which are not able to "find them self" when used as the query argument with one the find methods.
It's easily reproducible using the node.js native driver (first find the document using an id, then use the returned document as query to a new find), but can also be done using the mongo shell.
The following gist contains more information on the problem: https://gist.github.com/kapetan/652ebeac2be444f7bae6
production.zip in the gist contains one of the documents in question. This was tested with MongoDB 2.4 and 2.6.
This only applies to a couple of documents, but it can be consistently reproduced for those.
Has anybody seen something similar?
It's easily reproducible using the node.js native driver (first find the document using an id, then use the returned document as query to a new find), but can also be done using the mongo shell.
The following gist contains more information on the problem: https://gist.github.com/kapetan/652ebeac2be444f7bae6
production.zip in the gist contains one of the documents in question. This was tested with MongoDB 2.4 and 2.6.
This only applies to a couple of documents, but it can be consistently reproduced for those.
Has anybody seen something similar?
Reply all
Reply to author
Forward
0 new messages