3 ms·
This is something you might end up regretting later. It’s annoying adding another foreign key later and then having previously working queries fail at runtime
by aidos 4y ago
This is something you might end up regretting later.
It’s annoying adding another foreign key later and then having previously working queries fail at runtime due to an ambiguous join condition.
- paulhodge 4y agoAgree about not implicitly finding the join key. But as long as we're brainstorming imaginary features, then maybe as part of the schema, we could somehow declare the default join key to use, for any given two tables. In most cases it's pretty obvious what the best join key would be.