The Modeling Room: (M4) Handle realistic exceptions - (A21) Model many to many
Series: The Modeling Room, module 4, article 21 of 26. Keep 1 job charge while crediting 2 mechanics. Build a bridge table with its own row meaning, validate allocation weights that sum to 1, and keep participation counts and observed hours out of the money.
Who should read it?
Students learning modelstorming, analysts, report builders, data modelers working with business experts
Prerequisite
Keep one member's identity and one row meaning intact, as in article 20
Learning objective
Record who participated in a job while keeping its charge single, then decide what a report may count or allocate
Artifact
A job participation card with a bridge table, allocation rules, and validation tests
Why this matters
A job report that copies EUR 138.00 onto each of 2 mechanics shows EUR 276 for work that earned EUR 138. Payroll or customer credits built on that figure dispute badly, because the doubled money never existed. This lesson gives you the bridge that names 2 mechanics and still shows one amount.
What you'll learn
- How to list several participating mechanics for one job in a bridge table without copying its charge.
- How to agree allocation weights, keep participation counts labeled, and validate the joins before reporting.
Your output: a job participation card with a bridge table, allocation rules, and validation tests.
New terms: bridge and allocation weight