How to Model Approval Workflows in a Database Without Boolean Chaos A supplier application has been approved. Then its bank details change. Is the supplier still approved? The answer sounds like a business-policy question, but it quickly becomes a database design...
When Reference Data Changes: Designing Database Codes That Preserve History A shipping database contains an order from 2022 with the delivery method EXP. Today, EXP means “Express Delivery — next business day.” But in 2022, the same code meant “Express Delivery —...
When Your Data Sources Disagree: Designing a Database That Preserves the Truth A company is preparing to replace three old systems with one new database. The CRM says customer 1842 is called Northstar Labs. The billing system says Northstar Laboratories Ltd. A...
When “Current” Lies: How to Model Relationships That Change Over Time A support manager opens a customer record and sees that the account belongs to the Enterprise plan. Nothing looks wrong. Then finance asks a different question: “Which plan was this customer on when...
Your Schema Is Really a Theory of What Can Change A customer updates their company name. Should every invoice they have ever received change too? A product manager renames a subscription plan. Should last year’s revenue reports display the new name or the name...
Recent Comments