Document limitRequired and complexityEstimators flags#291
Document limitRequired and complexityEstimators flags#291
Conversation
Co-authored-by: Richard Sill <156673635+rsill-neo4j@users.noreply.github.com>
|
|
||
| It is intended for this feature to be used in conjunction with `limitRequired` to provide the most effective protection against unbounded queries. | ||
|
|
||
| When `limitRequired` is enabled, the complexity score of a query will be higher due to the multiplication by the provided `limit` arguments, which more accurately reflects the potential cost of executing that query. |
There was a problem hiding this comment.
| When `limitRequired` is enabled, the complexity score of a query will be higher due to the multiplication by the provided `limit` arguments, which more accurately reflects the potential cost of executing that query. | |
| When `limitRequired` is enabled, the complexity score of a query is higher because the provided `limit` arguments act as multipliers, which more accurately reflects the potential cost of executing that query. |
There was a problem hiding this comment.
this one has not been applied -
does the wording suggestion not capture the intended meaning?
There was a problem hiding this comment.
Hmmm I think it doesn't. It's not the score that's multiplied, the score is a result. It's the equation generating that result that involves multiplication with the limit arguments.
There was a problem hiding this comment.
ok, updated the suggestion
still wondering though - what could we call the things that get multiplied with the limit arguments? intermediate results or something like that?
There was a problem hiding this comment.
or maybe sth like "the provided limit arguments are multipliers"? And then we don't need a way to refer the intermediate results?
Co-authored-by: Richard Sill <156673635+rsill-neo4j@users.noreply.github.com>
3 participants
No description provided.