[views/primary] some inner sections should use the `limit` by default to avoid a denial of service (closes #2719110) Today, it is possible to call .related and get a huge unlimited database-dos-inducing resultset that will be nevertheless limited a bit further in pure python in the `autolimited` view. While we cannot completely avoid potential denial of services such as these we mitigate the problem with the default ui settings: if the inner vid is `autolimited`, then the relation result sets is computed using the user-defined limit. This change respects the semantics of the `autolimited` view and shouldn't break anything.

     1

sync_schema_props_perms('EmailAddress')

     2

     3

for source in rql('CWSource X WHERE X type "pyrorql"').entities():

     4

    sconfig = source.dictconfig

     5

    nsid = sconfig.pop('pyro-ns-id', config.appid)

     6

    nshost = sconfig.pop('pyro-ns-host', '')

     7

    nsgroup = sconfig.pop('pyro-ns-group', ':cubicweb')

     8

    if nsgroup:

     9

        nsgroup += '.'

    10

    source.cw_set(url=u'pyro://%s/%s%s' % (nshost, nsgroup, nsid))

    11

    source.update_config(skip_unknown=True, **sconfig)

    12

    13

commit()