Full sales DB tutorial

A sales database looks simple until you ask one question: if a customer buys three products in one order and pays in two installments, where does each fact go without getting duplicated or lost? Fatolu Peter’s walkthrough uses MySQL Workbench to answer that by splitting one business into linked tables instead of one giant spreadsheet. (dev.mysql.com) (x.com) MySQL Workbench is Oracle’s visual design tool for MySQL, and one of its core features is the Enhanced Entity-Relationship diagram, which draws tables as boxes and relationships as lines. Oracle’s manual says those diagrams show how tables connect and update alongside the model editor, so the picture and the schema stay in sync. (dev.mysql.com 1) (dev.mysql.com 2) The first box in a sales system is usually customers, because a sale starts with a person or company you can identify. That table holds one record per customer, which prevents the same name, email, and phone number from being retyped into every order row. (databasestar.com) (x.com) The next box is orders, and it exists because one customer can place many orders over time. In MySQL Workbench, that link is modeled as one-to-many, which Oracle documents in the Relationship Editor as a standard cardinality choice between one-to-one and one-to-many. (dev.mysql.com) (x.com) Products need their own table for the same reason customers do: one product can appear in hundreds of orders, so its name and price should live in one place. A retail sales schema on GitHub that follows this pattern separates customers, products, and orders, then uses queries on top of that structure for revenue and top-product reports. (github.com) (x.com) The tricky part is the space between orders and products, because one order can contain many products and one product can appear in many orders. That is why sales databases usually add an order-items table in the middle, which works like a receipt line: one row for one product, one quantity, one price inside one order. (github.com) (dev.mysql.com) Payments are usually separated from orders because the money trail does not always match the shopping trail. One order can be paid once, split across multiple payments, or left pending, and keeping payments in their own table makes those states queryable without rewriting the order itself. (github.com) (x.com) Employees belong in the model because sales systems do not just track what was bought; they also track who handled the transaction, updated the order, or owns the customer account. Once employees are linked to orders or payments, the same schema can answer team questions like which staff member processed the most revenue in a month. (x.com) (dev.mysql.com) What Peter is really teaching with the diagram is foreign keys, even if a beginner first sees only boxes and lines. Database Star’s MySQL Workbench guide shows that when you define a foreign key, the diagram updates automatically, turning an abstract rule like “this order belongs to this customer” into something you can see. (databasestar.com) (dev.mysql.com) That visual step is why a full sales example works better than toy tables with names like table1 and table2. When the boxes are customers, orders, products, payments, and employees, a learner can map each relationship to a real checkout flow and then write Structured Query Language queries that match how a business actually runs. (databasestar.com) (x.com) By the time the model is finished, the database is doing two jobs at once: it stores data, and it teaches structure. Oracle describes modeling as a way to visualize requirements and resolve design issues before or alongside building the database, and Peter’s video demo turns that into a beginner lesson you can watch instead of just read. (dev.mysql.com) (x.com)