Menu

Post image 1
Post image 2
1 / 2
0

Coding Cat Oran S2 Ep5 — The Many-to-Many Disaster

DEV Community·SysLayer·17 days ago
#ZvEUizwI
#webdev#database#sql#career#oran#table
Reading 0:00
15s threshold

The report table is agreed. No one is responsible for it. This is a different problem. The table looked clean on the whiteboard. Seventeen columns. One row per batch. Every department's data, agreed, signed, version-numbered. Oran had been looking at it for three days. He had a document called Problems with this table. It had eleven items in it now. He was still finding more. Problem 1: One batch, many inspections. QA inspects at three stages: incoming material, in-process, and final. Each stage produces a separate inspection record. Each record has its own result, its own inspector, its own timestamp. The current table has one row per batch. One inspection_result column. One inspector_id . One inspected_at . Which inspection result goes in the row? Oran sent an email to QA. QA replied: "Show the final result.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More