concept traditional database in category ios

appears as: traditional databases, traditional database
iOS 7 in Action

This is an excerpt from Manning's book iOS 7 in Action.

Imagine you have an application that catalogs people at specific companies. You can have two types of objects, Employee and Company. The relationship between these two objects would mimic real life by specifying that one company can have many employees. This inherently means that an employee essentially belongs to a company. In a traditional database there would be one table for employees and one for companies. Each table would contain rows of data for each individual record. For instance, the companies table would have rows that contain records for each different company. Each record within each table would have its own unique identifier, which is most commonly represented by a number.