--check-db-only

Check the database for consistency, e.g. duplicated IDs. Don't do anything else, including ID extraction, which must have been done previously.

Normal full-directory builds cache successful database checks in the local SQLite database. The CLI logs each file as it is checked and stops at the first failure. Successfully checked files remain cached even if a later file fails, so rerunning reaches the failing file faster; the failing file's reference changes are rolled back and unchecked files are not marked successful. Text and link edits recheck the changed files, while changes to available IDs, synonyms, the parent tree, configuration or checker code invalidate the broader cache. Media-file existence and cross-file duplicate tags are still checked for cached files. This also applies to the local preparation of -W, --web uploads, not the server-side build jobs. Use --check-db-only to force a complete database check without using the cache.

The initial use case was for usage in Parallel builds.