System-wide default paging/row limit

Hi,

is there a way to define default/implicit paging limits some way? Because if I have a database with a million records and a client sends a query like:

query {
    publication {
        id
        title
    }
}

… it would return a million items as result. It would be great if I could set an overall limit or a per table limit on the number of elements that can be returned in a single query. Let’s say I set the max paging limit to 100, with that setting a query without an explicit limit would become

query {
    publication(limit: 100) {
        id
        title
    }
}

Also this would prevent malicious clients setting too big limits. So, even if the query is

query {
    publication(limit: 50000) {
        id
        title
    }
}

it would become:

query {
    publication(limit: 100) {
        id
        title
    }
}

Is there such a mechanism in Hasura?

[0x777]

This should be fairly trivial to add (buildSelPermInfo has to change), the behaviour should be as follows: if the global_limit is set, it is used when limit is not specified in select permission definition, however if limit is specified in a select permission definition, it takes precedence over global_limit.

[rikinsk]

Hi. There is no way to set a blanket value for this setting across all queries. But https://docs.hasura.io/1.0/graphql/manual/auth/authorization/permission-rules.html#row-fetch-limit would be of help. You can set the limit for a table / role tuple. This will provide you with a more granular control over what roles can fetch how much data of a particular type in a single request