Skip to content

master-part spec: state that a dependency on the master implies its parts #222

Closed

Description

@dimitri-yatsenko

The book (30-design/053-master-part.ipynb) teaches that a dependency on a master is transitively a dependency on all of its parts — referencing the master guarantees every part row exists. This is a design consequence downstream tables rely on.

reference/specs/master-part.md covers structure, delete, and query semantics but does not state this transitive-completeness guarantee.

Proposal: add a subsection to reference/specs/master-part.md stating the guarantee, and a short note in how-to/master-part.ipynb.

From an internal datajoint-book → docs coverage review (priority P6).

Activity

  1. dimitri-yatsenko commented on Jul 21, 2026

    @dimitri-yatsenko
    MemberAuthor

    Addressed by #226, which added the transitive-completeness subsection to reference/specs/master-part.md — a dependency on the master is a dependency on all of its parts. Closing.

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

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions