Does every database table require a primary key? Explain why or why not and provide an example.
Do you believe that REA modeling will become a standard for developing & implementing accounting information systems?
Why or why not?
answer both questions with paragraph, ill give thumbs up 😉
The primary key of a database is a unique identifier; it uniquely identifies each record in the DB.
Selecting the primary key is one of the most, if not THE most important factor that determines the utility of the DB.
This serves as unique links to the other tables, that are also using the same.
- In fact, If a particular table design does not need a primary key, it may be deeply flawed !
- Something is missing, & leading to maintenance of identical records.
Let’s say we have an EMPLOYEES table that contains a record of each employee of the firm. Then, the employee ID is a GOOD choice for the primary key. Names, ages, etc are all repeatable, hence not useful as primary key
PART TWO :
REA modeling will NOT become a standard for developing & implementing accounting information systems, since there cannot be one basic REA diagram that would work for all businesses, because all businesses differ in:
- not only their business practices, but also
- their HR practices,
- the type of goods & merchandise that they deal in, &
- in the capacity of the HR that it has hired.
HOWEVER, since REA is now recognized, by industry standards, as useful enterprise modeling framework its advantages may outweigh the limitations, ot its limitations may be mitigated by new & modern evolved systems.