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.
Support for IQueryable<T> providers that do not support LongCount
See original GitHub issueIs your feature request related to a problem? Please describe.
I am trying to use HotChocolate with Azure CosmosDb via DocumentClient, which supports
IQueryable<T>. Unfortunately, although Count is supported, LongCount is not, so I get an error when I try to add pagination to a field. This happens at https://github.com/ChilliCream/hotchocolate/blob/b9ddf60a35f64527e9b49c527fdd62e2946ce28b/src/Core/Types/Types/Relay/QueryableConnectionResolver.cs#L52
Describe the solution you’d like
I would like QueryableConnectionResolver<T> to use or fall back to Count if LongCount is not supported.
Describe alternatives you’ve considered
It would be nice if DocumentClient and friends dealt with this themselves 😃
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes we were testing that already in a private beta with Microsoft. Still we need to write some integration tests for cosmosDB and use the IntCount since not all databases support the long count. This one is not yer implemented but I think will follow in the next two previews of version 9 probably preview 30. Version 9 should be finished in the next two weeks. We are heavily working one the new documentation which will pick up lots of new areas.
This one is now fixed with preview.40.