在 mongodb 前夕 API 级别禁用寻呼
Disable Paging on eve mongodb at API level
所以我有一个 API 像这样的东西
http:exmaple.com/people
当我使用它来检索数据时，响应被限制为每页 25 个条目。我想一次接收所有数据，即绕过分页。我无权访问服务器。这个怎么做。我尝试放置 ?page=all 和更多 stuff.But 似乎没有任何效果。我试过 max, skip 但那些也没有效果。
有许多（服务器）设置允许 API 维护者打开和关闭分页功能。引用自 docs:
PAGINATION. True if pagination is enabled for GET requests, otherwise False. Can be overridden by resource settings. Defaults to True.
PAGINATION_LIMIT. Maximum value allowed for QUERY_MAX_RESULTS query parameter. Values exceeding the limit will be silently replaced with this value. You want to aim for a reasonable compromise between performance and transfer size. Defaults to 50.
PAGINATION_DEFAULT. Default value for QUERY_MAX_RESULTS. Defaults to 25.
OPTIMIZE_PAGINATION_FOR_SPEED. Set this to True to improve pagination performance. When optimization is active no count operation, which can be slow on large collections, is performed on the database. This does have a few consequences. Firstly, no document count is returned. Secondly, HATEOAS is less accurate: no last page link is available, and next page link is always included, even on last page. On big collections, switching this feature on can greatly improve performance. Defaults to False (slower performance; document count included; accurate HATEOAS).
如果您无权访问服务器，则无法在全局或端点级别禁用分页。
所以我有一个 API 像这样的东西
http:exmaple.com/people
当我使用它来检索数据时，响应被限制为每页 25 个条目。我想一次接收所有数据，即绕过分页。我无权访问服务器。这个怎么做。我尝试放置 ?page=all 和更多 stuff.But 似乎没有任何效果。我试过 max, skip 但那些也没有效果。
有许多（服务器）设置允许 API 维护者打开和关闭分页功能。引用自 docs:
PAGINATION. True if pagination is enabled for GET requests, otherwise False. Can be overridden by resource settings. Defaults to True.
PAGINATION_LIMIT. Maximum value allowed for QUERY_MAX_RESULTS query parameter. Values exceeding the limit will be silently replaced with this value. You want to aim for a reasonable compromise between performance and transfer size. Defaults to 50.
PAGINATION_DEFAULT. Default value for QUERY_MAX_RESULTS. Defaults to 25.
OPTIMIZE_PAGINATION_FOR_SPEED. Set this to True to improve pagination performance. When optimization is active no count operation, which can be slow on large collections, is performed on the database. This does have a few consequences. Firstly, no document count is returned. Secondly, HATEOAS is less accurate: no last page link is available, and next page link is always included, even on last page. On big collections, switching this feature on can greatly improve performance. Defaults to False (slower performance; document count included; accurate HATEOAS).
如果您无权访问服务器，则无法在全局或端点级别禁用分页。