I have an application that has a table currently Customer that has a non nullable field LocationId. It is a 1 to 1 relationship currently. We have determined that we have to decouple the LocationId as the Customer may not have a location. Right now the LocationId is a FK in the Customer table to a PK table called Location.
The question is this should we just make the LocationId a nullable field in the Customer table. This causes least impact on changes we need to make as we use Entity Framework in our app and it's everywhere. The other option is making a table called CustomerLocation that has the two PK fields CustomerId and LocationId and deleting it from the Customer table. This really looks to be a many to many although I can put a constraint on it. This though we have to in our app go after the FirstOrDefault record everywhere. If it is best to do it this way then we will just have to bite the bullet.
Any suggestions what is the best practice here? Having a nullable FK not sure is best but impact is higher on the app code.