Hello SQL database experts. I have found myself needing to add a lists table. I currently have a staff table, a phone table, and an email table. What I want to do is add a lists table used for exporting the staff to the appropriate lists (this is to be imported into our call service for closures and emergencies). My initial idea behind the list membership table layout is as follows.
- Membership_ID, BIGINT, NOT NULL, PRIMARY KEY AUTO INCREMENT
- Category_ID, INT, NOT NULL, FOREIGNKEY(Lists.List_ID)
- Staff_ID, BIGINT, NOT NULL, FOREIGNKEY(Staff_Information.Staff_ID)
- Building_ID, INT, NOT NULL, FOREIGNKEY(Building_Information.Building_ID)
Now I have seen tables that do not have a primary key for the table. What are the problems associated with not having a primary key for a table like this? The list membership table is likely not to change much so...
