On my database structure in SQL Server, I have 3 types of products which requires different information about the order. So, I created one
Customers table and three different orders tables:
OrdersForProductCs. All orders table has one to many relationship on
I also have another table which is
Payments and will hold the payment details inside. But I have doubts here on how to structure it.
As I have multiple product types and a customer may have orders for multiple products at the same time, I need to relate those three order tables to
The other issue is that a customer may have an order for only one type of product. So, the FK columns on
Payments table needs to be
My question is whether those
nullable FK columns would be a headache for me on the long run or not? Generally speaking, would it be considered as a bad practice to have nullable FK columns on a table?