Pagination total count behavior across different service adapters

Direct Answer

Feathers v5+ documents a single, service-level option to control the total field: paginate.disableCount. When set to true, the framework skips the separate count query that SQL and MongoDB adapters normally execute. The memory adapter continues to return a total because it can compute it in-memory without extra I/O. If you turn pagination off entirely (paginate: false), the response becomes a plain array with no pagination metadata at all.

Confirmed Behavior

• disableCount: true – Adapters that issue a distinct count query (Knex, Sequelize, MongoDB, etc.) omit it; the total property is absent from the pagination envelope.
• disableCount: false (default) – Every paginated find triggers a count query; total is always present.
• Memory adapter – Ignores the flag; it always returns total because the dataset is already in memory.
• paginate: false – No pagination envelope, no total, just [item, item, …].

Configuration Steps

1. Open the service registration (typically in src/services//.class.ts or the generated service file).
2. Pass the paginate option with disableCount: true:

   app.use('messages', new MessageService({
     paginate: {
       default: 25,
       max: 100,
       disableCount: true
     }
   }));

3. Restart the app and issue a paginated request:

   GET /messages?page=1&perPage=10

4. Verify the response lacks a total field inside pagination.

Adapter-Specific Caveats

• Not every community adapter respects disableCount. Check the adapter’s README or source for a conditional if (!params.paginate?.disableCount) await this.Model.count… pattern.
• Some adapters may throw if they receive an unknown option; test after upgrading Feathers or the adapter.
• Client code that reads response.pagination.total will break—plan a migration or provide a fallback.

Verification Checklist

• Confirm Feathers version ≥ 5.0 (npm ls @feathersjs/feathers).
• Inspect the generated SQL (enable query logging) to ensure no SELECT COUNT(*) runs.
• Run the same request against a memory-backed service to confirm total still appears there.

One Diagnostic Detail Needed

Which specific database adapter (e.g., @feathersjs/knex, feathers-mongoose, feathers-mongodb) are you using? A few community adapters still require a custom patch to honor disableCount.