A little background
We are adding a new feature to our software which allows users to enter text for a specific Customer or Location. The software will then read these from the database when a Customer or Location is chosen, and display the appropriate text in a pop-up window. Locations must have a Customer but a Customer can have no Locations. There are two scenarios that we would show these notifications:
- A Customer is selected from a drop down control and the software will look up any notifications for that Customer.
- A Location is selected from a drop down control and the software will automatically select the associated Customer and display any notifications for both.
I originally thought about creating two tables:
LocationNotifications, but when I added the fields for both, I realized the only difference is one table references a CustomerId while the other references a LocationId:
I was thinking of combining the two to look like this:
NULL on both CustomerId and LocationId in case the notification is for one specifically. Is this the best approach or should I keep the table separate? Will I run into join issues if trying to retrieve both notifications but one is
My past tells me I have more flexibility with two tables but the "normalization" in me wants to try to condense them.