$ne doesn't work with null
See original GitHub issueDescribe the bug Try to filter some entities where some field isn’t null. Obvious query will be
find<Entity>(Entity, {field: { $ne: null }})
But typings doesn’t allow it and generated query is also wrong. Seems the only workaround is to use use $and
with combination with $not
that looks too boilerplated.
Any suggestions?
Versions
rc5
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Filter Query ne null doesnt work - Power Platform Community
Solved: I'm building a flow that pulls a spreadsheet into a list. However I cannot guarentee that the source spreadsheet (table) WON'T contain...
Read more >Why does $ne comparison against null not work in a $filter ...
It is just the $ne that is not working. I am running this query on Mongo 4.4 series. First, see https://docs.mongodb.com/manual/tutorial/query- ...
Read more >Mongo {$ne : null} not working as expected - Stack Overflow
I was able to reproduce the problem on MongoDB version 2.4.9. > db.sourceListings.findOne({displayed:{$ne:null}}); { <.. other stuff went ...
Read more >NULL vs INITIAL - SAP Community
NULL values for a field means that physically nothing is stored. This only happend when a new table field is appended for an...
Read more >PostgreSQL: IS NOT NULL - TechOnTheNet
If expression is a NULL value, the condition evaluates to FALSE. Example - With SELECT Statement. Here is an example of how to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, is this fixed?
Will be fixed in next RC.