I\'m defining a database for a customer/ order system where there are two highly distinct types of customers. Because they are so different having a single customer table wo
A foreign key can only reference a single primary key, so no. However, you could use a bridge table:
CustomerA <---- CustomerA_Orders ----> Order CustomerB <---- CustomerB_Orders ----> Order
So Order doesn't even have a foreign key; whether this is desirable, though...