1.3.0: document the manager hot-swap reload pattern
Typed References gains "Surviving a reload" (replace/managerReplacing,
the mandatory clearCache and the flush -> clearCache -> close order);
Gotchas pins the memoized default-policy staleness of a ref that
crossed a swap. Coordinates bumped to 1.3.0.
Stop saying the file backends have no push feed
They gained one in 1.2.0 - the operating system's own watch service -
and a version stamp taken from the file, so polling over them detects
updates and not only deletes. Six pages still described the state before
that: the per-backend matrix, the push-vs-poll rule, two capability
tables, and the "see also" line on both file-backend pages.
H2 keeps the deletes-only caveat, which is true of H2 alone: it is the
one backend reporting version 0 for every key it holds.
Also bumps the artifact coordinates to 1.2.1, and renames the
heterogeneous-backend "fan-out" after the term stopped naming one thing.
Bump wiki artifact coordinates to 1.2.0
Bump wiki artifact coordinates to 1.1.0
Update the install coordinates to 1.0.9
manager: note dirty cells are pinned against LRU eviction; bump coordinates to 1.0.8
Tighten and fact-check every wiki page (concision + correctness pass)
Swept all 41 content pages for concision (cut rambling/hedging/repetition, prefer scannable
tables and short sentences) and verified every load-bearing technical claim against the source.
Real fixes: Local-Files documented the removed prettyPrint/fsyncEvery LocalFileConfig constructors
(gone since 271962d) - rewritten to the one-arg config; Grouped-Files' stale cross-refs to those
knobs corrected. Added a few source-backed facts that were missing (nested inTransaction throws,
duplicate migration version rejected at register(), getAll never returns null). No behavior claims
changed beyond matching the code.
docs: sync wiki with current code — grouped-file backend, versions, capability accuracy
New page:
- Grouped-Files.md — the key-major aggregate-file backend (one file per key,
every collection as a sub-node; FileKeyNames sanitisation; atomic writes;
SchemaAware via _schema/migrations.json; full-scan queries with declaration
validation; no transactions; versions() = 0), plus a _Sidebar entry.
Factual fixes across the wiki against the current code and libs.versions.toml:
- Seven backends everywhere (GroupedFile added to matrices/lists); the
"six backends" phrasings that were specific to MultiBackendRefExampleTest and
the six-key example were left correct on purpose.
- Single Java 25 toolchain build (sourceCompatibility=25 + options.release=8,
Jabel FinalCraft fork) — removed the stale JDK-17 compiler-pin / ~/.jdks blocks.
- Dependency and project versions: Jackson 2.22.0, mongodb 5.8.0, mysql 9.7.0,
postgresql 42.7.12; project coordinates bumped to 1.0.6.
- YAML accepted by both file backends (LocalFile and GroupedFile); Mongo stores
the key as the document _id (not storage_key); health() returns HealthStatus;
InMemory implements SchemaAwareStorage; ChangeFeed = Mongo/PostgreSQL/InMemory.
- CachingManager.stats()/CacheStats section; RefRegistry rejects a conflicting
duplicate registration; Mongo replica-set / open-no-auth test creds.
- Fixed a few broken examples/links: GuildManager two-arg constructor,
Quick-Start variable/type names, BatchSaveReport/KeyOutcome shown as final
classes, a dead Caching-Managers wiki-link.
docs: bump version coordinates to 1.0.4
docs(manager): absorb cachedValues() and the add-on Maven snippet from the module README
Remove standalone module and make manager does not expose core module
Add complete EveryDatabase dev-guide wiki
Home, sidebar, footer, and every section page — Getting Started, Core Concepts,
Working with Data, Backends, the Manager module (per-context RefRegistry),
Operations, Advanced, Reference, and Contributing. Conventions in
specs/SPEC_wiki.md; content grounded in the repo sources and reviewed for
accuracy against them.