layout | root | title | minutes |
---|---|---|---|
lesson |
. |
Supplement - Database design |
30 |
- Order doesn't matter
- Every row-column combination contains a single atomic value, i.e., not containing parts we might want to work with separately.
- One field per type of information
- No redundant information
- Split into separate tables with one table per class of information
- Needs an identifier in common between tables – shared column - to reconnect (foreign key).
- Access or Filemaker Pro
- GUI
- Forms w/QAQC
- But not cross-platform
- MySQL/PostgreSQL
- Multiple simultaneous users
- More difficult to setup and maintain