adding ModifyPagingOptions causes the follow error: "The maximum allowed type cost was exceeded"
msheluga opened this issue · 11 comments
Product
Hot Chocolate
Version
14.10
Link to minimal reproduction
https://github.com/msheluga/HC14Test
Steps to reproduce
the project does require the Adventureworks2022 DB which is located at https://learn.microsoft.com/en-us/sql/samples/adventureworks-install-configure?view=sql-server-ver16&tabs=ssms
-
when the graphql server is running execute the following query
`query {
address(order: [{ addressID: ASC }]) {
nodes {
addressIDcity
}
}
}
`
error will occur
What is expected?
pagination to function as it did in V13 where the SetPagingOptions modified the paging attributes without errors about the cost. It should return 100 records .
What is actually happening?
Modifying the Paging options as described in the documentation causes the following message
"message": "The maximum allowed type cost was exceeded."
this also occurs if you modify the DefaultPagingSize in the attribute i.e. [UsePaging (DefaultPageSize =100)]
if all paging is removed it will return all 32521 records
Relevant log output
Additional context
No response