Despites the Defer, Subscriptions, Versioning, Multi requests and merge results and other out of the boxes that GraphQl has over OData what really interests me (in this example using HotChcolate and EF Core) is a comparison of the less messy(grotesque, horrible, scare, slow as hell) SQL result from the Expression auto generated from complex queries to the queryable provider.
Why there is no talk about odata?
Despites the Defer, Subscriptions, Versioning, Multi requests and merge results and other out of the boxes that GraphQl has over OData what really interests me (in this example using HotChcolate and EF Core) is a comparison of the less messy(grotesque, horrible, scare, slow as hell) SQL result from the Expression auto generated from complex queries to the queryable provider.
Awesome. I really see a ton of use cases for GraphQL with EF.
Very nice and informative.
Seems able to replace views in db
Can we get this sample code?
github.com/JeremyLikness/dotnetconf2021
@@JeremyLikness thanks!!!
Super
Can you copy paste? :)