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

Not handling nulls like in Mongo #33

Open
datanotion opened this issue Mar 31, 2016 · 0 comments
Open

Not handling nulls like in Mongo #33

datanotion opened this issue Mar 31, 2016 · 0 comments

Comments

@datanotion
Copy link

Does meteor-aggregate handle a ​_null_​ in an aggregate query different than native Mongo? I have a query that runs fine in Mongo, but returns no records in Meteor using this library. Once I remove the match on a field that is Null in the database, it runs just fine.

Super-simplifed version of the query:

db.expenses.aggregate(
[
{"$match":{
"details.account_number":10940,
"details.vendor_id":null,
"details.dept_id":1}
}
]
)

But once I remove the vendor_id match, then Meteor returns the records.

Is this a bug, or by design?

Thank you.

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

No branches or pull requests

1 participant