Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature Request: Allow passing multiple predicates
See original GitHub issueIt would be great if there was a fetchContacts() method allowing the caller to pass multiple predicates. Or an additional predicate which searches over all fields of the contact.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Optimization Tips for Multiple Range Predicates, Part 3
Run the following code to enable I/O statistics: SET STATISTICS IO ON;. For the first page request, you call the procedure without passing...
Read more >Can I apply multiple predicates to an NSFetchRequest ...
Yes it's possible. You're looking for compound predicates and here's an example with AND predicates:
Read more >[feature] Support for "OR" condition on multiple filter predicates.
Currently filter objects can have one or more query objects but they work with AND it would be great to somehow switch to...
Read more >injection - mountebank
Unlike other predicates, predicate injections bind to the entire request object, which allows you to base the result on multiple fields.
Read more >Feature Request: Predicate pushdown - FoundationDB Core
Feature Request : Predicate pushdown ... This would allow multiple different filter processes to live on the same machine at different ports.
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
That’s good news! There was some confusion with the official documentation as it says the filter is used for contact names which doesn’t seem right. I’ll address that with a proper name asap 😃
Regarding the performance, I believe it is very related to your other issue so we’ll takle it there.
Keeping this issue open until the naming is merged
This is now merged to
main. It will be available in 1.4.0 without breaking changes. Closing as done