Skip to content

Preserve native loaded-state aliases for canonical named relations #242

Open

Description

@philipgreat

Finding

The latest generated relation metadata uses canonical school_list; the
runtime-owned Java example previously accepted isPropertyLoaded("schoolList").
Fixed fields already share one bit across canonical/member/column aliases, but
named relations lack the corresponding alias normalization. Changing the
example assertion to canonical spelling would drop its existing native-API
coverage instead of preserving the contract.

Bounded correction

  • Derive a value-free canonical/native relation-name map once per FieldLayout.
  • Normalize named selections at projection, update and lookup boundaries;
    retain only one canonical marker, never two markers per row.
  • Keep fixed-field bit lookup and literal #dynamic_field codes unchanged.
  • Restore the existing Java-member assertions, add focused geometry tests,
    and rerun the existing generated graph gate.

This is separate from the E exception-path naming decision and does not choose
that policy. Tracked with teaql/teaql-conformance#210. Local validation only;
no publication, tag push or formal P1 merge.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions