Skip to content

Repository files navigation

cquarry logo

cquarry

Canonical Calibre database layer and search grammar engine for Calibre libraries.

PyPI Python CI MIT License zero dependencies

This library powers CalibreQuarry (CLI/TUI), Hermitage (GTK4 gallery), Carrel-calibre-web (web reader), and bindery-cli (EPUB repair & audit). By centralizing the search grammar parser and metadata access, cquarry evaluates virtual library definitions and search queries consistently across frontends.

Features

  • Direct SQLite access. No calibredb binary required, no Calibre Python initialization overhead.
  • Coherence on demand. Caches are lazy and cheap, and CalibreDB.refresh() clears them all in one call, so a connection held open across an external Calibre write never contradicts itself. One boundary: when the connection rides a locked-database snapshot copy, the snapshot is not retaken; reopen for truly current data.
  • Lock-safe snapshots. Automatically detects if Calibre holds an exclusive write lock on metadata.db and routes queries through a temporary consistent snapshot (sqlite's backup API; backup_to() gives the same consistency to consumer backups). external_changes_detected() tells a long-lived holder when its caches have gone stale.
  • Full search grammar parity. A recursive-descent parser implementing Calibre's native search capabilities: boolean logic, field prefixes, date math (hyphen and slash separators), hierarchical tags with ./.. component modifiers on every text field, custom columns, identifiers, saved-search interpolation (search:"Name"), multi-valued count operators (tags:#>3), language canonicalization (languages:English → eng), and nested virtual library cross-references. Adversarial grammar-valid queries surface as ParseException, never a raw RecursionError; an empty query after any location matches nothing; invalid boolean keywords raise; two-letter language codes canonicalize (languages:ja matches jpn); super-quotes """...""" shield quote- and paren-heavy queries from the lexer; and the vocabulary is upstream-strict (dates and numerics take exactly true/false as presence words), all verified against upstream.
  • Native page counts. The pages: location reads Calibre's own books_pages_link table first (maintained by upstream's CountPages integration) and falls back to an int custom column labelled pages; counts also ride along in every book row.
  • Entity secondary columns & display config. Book rows carry author_sorts/author_links parallel to authors; get_entities(kind) exposes {id, name, sort, link, count} for authors/series/publishers/tags/languages; custom columns report editable, normalized and their decoded display JSON (enum_values, enum_colors, …); and a typed preferences accessor covers everything else (get_preference, get_field_metadata, get_user_categories, get_tag_browser_state).
  • Metadata portability. Read e-reader annotations, per-device reading progress, third-party plugin data, and conversion profiles; sanitize comments HTML for display.
  • Book-content search. Calibre's full-text-search.db sidecar is a sanctioned read: get_book_text() returns a format's extracted plain text, search_book_text() runs a folded content search over it, and get_text_extractions() feeds integrity audits (find_failed_text_extraction reports the formats whose extraction failed: scans, DRM, corrupt files). No FTS5 machinery required.
  • Opt-in write path. cquarry.write.WritableCalibreDB offers trigger-safe mutations in a separate module the read-only API can never touch:
    • Field setters. Title, authors (with author_sort recomputation), series (+index), publisher, rating (UNIQUE-deduped, with clear_rating), languages (canonicalized to ISO codes), tags (add/remove/clear_tags for all at once), identifiers, comments, and has_cover.
    • Custom columns. Generic writes with storage layout auto-detected, enumerations validated against display.enum_values, non-editable columns refused, plus add_custom_column_values append semantics for multi-valued columns; schema management (create_custom_column/delete_custom_column, flag-only delete like upstream).
    • Books and formats. The creation path (add_book: trigger-filled sort/uuid, Author/Title (id) layout, atomic format/cover placement with truthful data rows, a dry-run plan, copy-only), format registration/replacement/removal, full book removal with orphan pruning, and undo-able format repair (save_original_format/restore_original_format).
    • Whole-library verbs. Entity-wide renames (rename_entity fixes a misspelled author everywhere, merging case variants), verbatim sort corrections, cover replacement (set_cover/remove_cover), and trash management (list_trash/empty_trash/expire_trash).
    • Calibre stays truthful. Every row-level mutation queues OPF resync in metadata_dirtied; renames re-lay the on-disk layout (the book directory and format stems move with the rows); format writes queue FTS re-extraction and pages rescans in the sidecar.
  • Context manager. CalibreDB supports with statements for automatic cleanup of snapshot files.
  • Zero dependencies. Pure Python 3.14+ stdlib (sqlite3, re, json, unicodedata).

Usage

from cquarry.db import CalibreDB

# Open a library (creates a snapshot if Calibre has the lock)
with CalibreDB("~/Calibre Library/metadata.db") as db:
    # Fetch all books with pre-joined metadata
    books = db.get_all_books()

    # Search using Calibre's native grammar
    sci_fi = db.search("tags:Fic.SciFi and rating:>=4")
    print(f"Found {len(sci_fi)} highly rated Sci-Fi books.")

    # Resolve a virtual library to a set of book IDs
    wing = db.resolve_vl("To Read")

    # Interpolate a saved search straight from Calibre's preferences
    award_winners = db.search('search:"Award Winners"')

    # Inspect custom columns (#label, bare label, or display name all work)
    cols = db.get_custom_columns()
    status = db.load_custom_column("#reading_status")

    # Single-entity helpers (no whole-library scan)
    book = db.get_book(42)
    epub = db.get_format_path(42, "EPUB")

    # Metadata portability
    highlights = db.get_annotations(42)
    progress = db.get_last_read_positions(42)
    wordcounts = db.get_plugin_data(name="wordcount")

The composed deep fetch combines metadata, formats, custom columns, and annotations:

dossier = db.get_book_dossier(42, include_comments=True)
print(dossier["formats"], dossier["custom_columns"])
print(dossier["comments"]["plain"])  # comments HTML, already stripped

Writes live behind an explicit opt-in import:

from cquarry.write import WritableCalibreDB

with WritableCalibreDB("~/Calibre Library/metadata.db") as wdb:
    wdb.add_tag(42, "Audited")
    wdb.set_identifier(42, "isbn", "9780123456789")
    wdb.clear_identifier(42, "mobi-asin")  # honest no-op when absent

# A multi-book curation pass commits exactly once; any failure (a Ctrl-C
# included) rolls the whole pass back, directories created inside it too:
with WritableCalibreDB("~/Calibre Library/metadata.db") as wdb:
    with wdb.batch():
        wdb.set_pubdate(42, "1991-10-01")
        wdb.add_tag(43, "Audited")

# Every mutation queues an OPF regeneration; check what Calibre will resync:
with CalibreDB("~/Calibre Library/metadata.db") as db:
    print(db.get_dirtied_books())  # e.g. [42, 43]

Installation

pip install cquarry

API at a glance

The full per-method reference lives in API.md. One line per module:

Module What it is
cquarry.db The read-only database layer (CalibreDB): hydrated rows, single-entity fetches, format/cover path resolution, custom columns, preferences, annotations and progress extractors, VL/saved-search resolution, and the composed get_book_dossier() deep fetch.
cquarry.search The lexer/parser/evaluator porting Calibre's search grammar; usable standalone behind the MetadataProvider protocol.
cquarry.helpers Domain utilities: rating conversion, comment sanitization, author display, series gaps, image dimension sniffing, the ISBN family (isbn_normalize, isbn_check_digit_is_valid, to_isbn13), and tag_rollup.
cquarry.integrity The shared library-integrity predicates: untagged, unrated, authorless, formatless, coverless, missing cover files, deprecated formats, low-res covers, duplicates, failed text extractions, series gaps, plus the metadata-quality trio (invalid UUIDs, sentinel pubdates, bad language codes).
cquarry.analytics Shared derivations: addition timeline, per-author stats, rating distribution, genre distribution (hierarchical tag shares), virtual library (wing) overlap.
cquarry.write The opt-in mutation path (WritableCalibreDB): trigger-safe setters, batch() transactions, remove_book, and the add_book creation path. Every mutation queues OPF resync.
cquarry.config Saved database-path configuration (~/.config/cquarry/config.json).

Development

python -m pytest tests/           # full suite
python -m pytest tests/ -v        # verbose

Run with PYTHONPATH=src to exercise this checkout rather than any installed copy.

Six test modules: test_db.py (CalibreDB against fixture databases), test_helpers.py (utility functions), test_search.py (parser, matcher, and integration tests), test_write.py (opt-in write module with trigger-hazard fixtures), test_integrity.py (library integrity predicates), and test_analytics.py (analytics derivations).

See spec.md for the full contract and roadmap.md for planned work.

Acknowledgements

Carrel-calibre-web is a fork of calibre-web that uses cquarry as its search and virtual-library engine. Features proven there flow back into cquarry's roadmap (see Phase 7); calibre-web's original authors deserve the credit for the web experience that fork builds on.

Support

If cquarry is useful to you and you'd like to chip in:

License

MIT. See LICENSE.

About

Canonical Calibre database layer and search grammar engine: read-only access by design, with an explicit opt-in write module for sanctioned mutations.

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages