Databases design - one link table or multiple link tables?
- by David
Hi there,
I'm working on a front end for a database where each table essentially has a many to many relationship with all other tables.
I'm not a DB admin, just a few basic DB courses. The typical solution in this case, as I understand it, would be multiple link tables to join each 'real' table. Here's what I'm proposing instead: one link table that has foreign key dependencies to all other PKs of the other tables.
Is there any reason this could turn out badly in terms of scalability, flexibility, etc down the road?