Validate the codeminer database for on-disk inconsistencies
Source:R/backend.R
validate_database.RdInspects the database at CODEMINER_DB_PATH and reports any
inconsistencies it finds — without modifying the database. The
specific checks depend on the backend:
Value
A named list of character vectors, one entry per kind of issue. Empty vectors mean no issues of that kind were found.
Details
codeminer_folder:orphan data files:
<name>.duckdbfiles at the folder root with no matching metadata row (typically left by a previousadd_*_table()that died after the data file was committed but before the metadata file was).dangling metadata: metadata rows that reference a data file that does not exist.
stale temp files:
*.parquet.tmp(metadata) or*.duckdb.tmp(data) files left over from an interrupted write.
duckdb_file:dangling metadata: metadata rows referencing data tables that do not exist in the file.
Issues are reported via informational messages. The function returns a named list of issues invisibly so callers can act on them programmatically.
See also
Other Database management:
update_lookup_metadata(),
update_mapping_metadata(),
update_relationship_metadata()