Currently the database contains something like so (these are the main fields but there's a large amount more):
+----------+----------------+----------+ | Agency | parent | main_term +----------+----------------+----------+ | 1 | Office Staff | Supplies | | 1 | Supplies | Postings | | 1 | Supplies | Artwork | +----------+----------------+----------+
The program would spit this data in a list like so, looking at the parent and main_term for proper indentation:
Agency #1: Office Staff --Supplies ----Postings ----Artwork
Right now the data seems redundant and creating a program for average users to edit or restructure the lists would turn out very confusing.
Is there a better way to structure this using multiple tables?
Thanks in advance.
Supplies
50 times in the table? Probably a lot more efficient to use surrogate keys for those instead of repeating the name so many times... – Aaron Bertrand♦ Aug 7 '13 at 15:39