Skip to content

test(db_get): multi-table root shares one root symfile#241

Merged
singaraiona merged 1 commit into
masterfrom
test/db-get-shared-symfile
Jun 11, 2026
Merged

test(db_get): multi-table root shares one root symfile#241
singaraiona merged 1 commit into
masterfrom
test/db-get-shared-symfile

Conversation

@ser-vasilich

Copy link
Copy Markdown
Collaborator

The three flat splayed tables (Trades/Quotes/Returns) under one root
each created a private per-table symfile for the same vocabulary.
Multi-table roots follow the client layout: one root symfile shared
via the explicit sym argument, so cross-table SYM ops stay on the
same-domain fast path instead of re-encoding positions between
per-table domains.

Asserts exactly one symfile exists at the root and none per table
dir; the overwrite-heal re-set appends to the shared vocabulary
instead of reseeding a private one.

Audited the rest of the rfl suite for the same pattern: parted
fixtures already share the partition root's symfile by convention
(date, integer, and dotted segments all verified), and the remaining
multi-symfile tests exercise symfile mechanics deliberately
(sym_coverage, db_sym_resolution, shared_sym_domain,
part_mixed_width, csv_splayed, system_branch_cov) — left untouched.

The three flat splayed tables (Trades/Quotes/Returns) under one root
each created a private per-table symfile for the same vocabulary.
Multi-table roots follow the client layout: one root symfile shared
via the explicit sym argument, so cross-table SYM ops stay on the
same-domain fast path.  Asserts exactly one symfile exists at the
root and none per table dir; the overwrite-heal re-set appends to
the shared vocabulary instead of reseeding a private one.
@singaraiona singaraiona merged commit 6c4b1ed into master Jun 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants