Reputation:
I have Subscribers, SKUs, and Subscribers To SKUs. The SKUs table will be around 75,000 - 100,000 entries, and each subscriber could subscribe to any/all of them. So the Subscribers To SKUs table could get ridiculously large. Is there a better way to approach this other than a many-to-many table relationship?
Upvotes: 0
Views: 132
Reputation: 499002
A many-to-many table is the right approach. This is how such relationships are modelled in a relational database.
If this table is indexed correctly, even with millions of records you shouldn't have performance issues.
Upvotes: 4