api with pagination, why occur database query with limit 1000

[flyly0755]

with this api http://127.0.0.1:8123/api/regioninfo/?page=3 ,there are 3 database query show as debug_toolbar:

1. SELECT COUNT(*) AS "__count" FROM "regioninfo_region" get total number for knowing how many pages these are.

2. SELECT "regioninfo_region"."id",       
   "regioninfo_region"."name",       
   "regioninfo_region"."name2",       
   "regioninfo_region"."pinyin",       
   "regioninfo_region"."parent_id",       
   "regioninfo_region"."deep",       
   "regioninfo_region"."ext_id",       
   "regioninfo_region"."remark"  
   FROM "regioninfo_region" LIMIT 50 OFFSET 100
   this is also can be understand, one api query get back 50 data.

3. SELECT "regioninfo_region"."id",
   "regioninfo_region"."name",
   "regioninfo_region"."name2",
   "regioninfo_region"."pinyin",
   "regioninfo_region"."parent_id",
   "regioninfo_region"."deep",
   "regioninfo_region"."ext_id",
   "regioninfo_region"."remark"
   FROM "regioninfo_region" LIMIT 1000
   how about this query, why with same query as step 2 except limit condition?

[hudy0]

Make sure that you are running your SQL in the same thread that handled the request.

The Django debug toolbar only seems to take a look at the SQL statements that are run in the current thread and assumes that these are the only ones that are related to the request that was handled.

[flyly0755]

yes, all these 3 sql query are in the same thread related with one same api call.

[tomchristie]

When you're using the browsable API you may have other database queries that are required in order to generate the form controls.

I expect there's a select dropdown on that page, which is rendering a choice of regions to select from.

Issuing a request to that endpoint using JSON may not make the same number of queries.

[flyly0755]

Yes，you are right👍 but how i change the limit number 1000? for example, change it to 100 for reducing database stress.