Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query for Null or Missing Fields #54

Closed
ericfong opened this issue Jul 19, 2017 · 2 comments
Closed

Query for Null or Missing Fields #54

ericfong opened this issue Jul 19, 2017 · 2 comments
Labels

Comments

@ericfong
Copy link

Thanks for your package first. That is really amazing.

I found that the behavior of find({ someField: null }) is not same as mongodb

https://docs.mongodb.com/manual/tutorial/query-for-null-fields/

in which null should also match with undefined field.
Shall mingo align that with mongoDb spec? Or that is expected behavior?

BTW. I have done a little benchmark and found that is much faster than sift and within same level as nedb and lokijs. Thanks a lot.

@kofrasa kofrasa added the bug label Jul 19, 2017
@kofrasa
Copy link
Owner

kofrasa commented Jul 19, 2017

Hi @ericfong ,

Thanks for reporting this, it is definitely a bug. I am doing some work to move into the new age of es6 ;) so I should be able to throw in a fix fairly quickly, however a pull request is also welcome.

I appreciate the tiny benchmark done. I am happy to know Mingo is not lagging behind in performance given I have mostly prioritized features and MongoDB compatibility. :)

@ericfong
Copy link
Author

Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants