FA-143 / Storage and queries / Member archive

A joined row loses a field when two columns share a label · case 03

Converting a joined result into an object overwrites one table's identifier with another table's identifier.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Each projection entry is [relation_alias,column_name] and has a matching value. Pairs are unique; components contain no dots. Return a map keyed by relation_alias + '.' + column_name, retaining every value including NULL and zero.

Why this case matters

Models client-side hydration of relational join results. It illustrates loss of provenance and stable field names when mapping column arrays into objects; it does not infer table names from database drivers.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
joined identifiers both survive	`{"id": 4}`	`{"orders.id": 3, "users.id": 4}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.