Theory
The line item with no life of its own
In Meera's design, a Customer clearly stands alone: give it a customer number and it exists, full stop.
But consider a single line on an order, '2 kg sugar'. Does 'line 1' mean anything by itself? No, line 1 of which order? It cannot exist, or even be identified, without its parent order.
Some entities are self-sufficient; others are utterly dependent. Databases name this strong vs weak entities, and it changes how you identify them. Meera's orders will show you exactly why.
Theory
A person vs a hotel room number
A person has an identity of their own, an Aadhaar number identifies them anywhere (strong entity). But 'Room 101'? Room 101 of which hotel? The room number only means something inside a particular hotel; on its own it is ambiguous (weak entity). To identify the room you need hotel + room number together. Weak things borrow their parent's identity to become unique.
Theory
The two, precisely
- Strong entity: exists independently and has its own key (a primary key attribute). Customer, Item, Order. Drawn as a single rectangle.
- Weak entity: cannot exist or be identified on its own; it depends on a parent (owner) entity. It has only a partial key (a discriminator) that is unique within its parent. Its full identity = parent's key + its own partial key. Drawn as a double rectangle, joined by a double-diamond identifying relationship.
An Order Item is weak: it needs its Order to exist, and 'line 1' is unique only within that one order.
Quiz
Why is an 'Order Line Item' considered a WEAK entity?
- It cannot exist or be uniquely identified without its parent Order
- It has too few attributes to be strong
- It is stored in a smaller table
- It has no relationships at all
Show the answer
It cannot exist or be uniquely identified without its parent Order
A weak entity is existence-dependent on a parent: an order line has no meaning without its order, and 'line 1' is unique only within a given order, so its own attributes cannot identify it alone. It borrows the Order's key to become unique. Weakness is about identity dependence, not size or attribute count, which is the exact misconception the wrong options carry.
Think first
How do you identify a weak entity?
Two different orders each have a 'line 1'. If a weak Order-Item's partial key is just the line number, how does the database tell the two 'line 1's apart? What full identity does it use?
Show the answer
It combines the parent Order's key + the partial key: 'Order 5001, line 1' versus 'Order 5002, line 1', now unique. The line number alone (the partial key / discriminator) repeats across orders, so it is only unique within one order. The full identity of a weak entity is always owner key + discriminator, exactly how hotel + room number identifies a room.
Watch out
Where marks leak
Thinking 'weak' means 'small' or 'unimportant', it means existence-and-identity dependent on a parent. Forgetting the partial key (unique only within the parent) and that full identity needs parent key + partial key. And the diagram symbols: strong = single rectangle, weak = double rectangle with a double-diamond identifying relationship. Exams reward the correct symbols and the parent-key identification rule.
Theory
This is why keys matter next
Notice the theme: identifying things uniquely is the beating heart of databases, a customer number, an order number, a parent key plus a partial key. The next lesson makes 'identity' precise with the full family of keys: super, candidate, primary, composite, foreign, unique. Weak entities are your first hint that choosing the right key is the central design skill. Next: attribute types, then the keys themselves.
Summary
Key takeaways
- A strong entity exists independently and has its own key (Customer, Item); single rectangle.
- A weak entity cannot exist or be identified without a parent (Order Item needs its Order); double rectangle.
- A weak entity has only a partial key (discriminator), unique within its parent.
- Its full identity = parent's key + partial key.
- Weakness is about identity dependence, not size.
- Memory hook: a person (strong) vs hotel Room 101 (weak, needs the hotel too).