meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years |
| seen | Mar 25 at 15:18 | |
| stats | profile views | 1 |
|
Feb 27 |
awarded | Notable Question |
|
Jun 23 |
awarded | Popular Question |
|
May 19 |
awarded | Notable Question |
|
Dec 29 |
awarded | Popular Question |
|
Sep 8 |
awarded | Supporter |
|
Sep 2 |
asked | Reasons against using local indexes |
|
Jul 5 |
accepted | Oracle - Automate Export/Unload of Data |
|
Jun 30 |
asked | Oracle - Automate Export/Unload of Data |
|
May 19 |
comment |
Relational Design - Multiple tables into one foreign key column? Although cows and pigs have similar bodies, the names of their cuts differ (beef chuck vs. pork butt). And both are completely different from poultry. Also, AFAIK, all poultry cuts are named the same, no matter the type of bird (chicken breast, turkey breast, etc.), which is why there's a "bird_id" foreign key column on the "poultry_meats" table. In practice, I would go in a similar route as you suggested, but this question is just for theory. |
|
May 17 |
awarded | Scholar |
|
May 17 |
accepted | Relational Design - Multiple tables into one foreign key column? |
|
May 17 |
comment |
Relational Design - Multiple tables into one foreign key column? Thanks for the answer. This seems to be what I'm looking for, but I'd like to research it further before I accept. |
|
May 17 |
comment |
Relational Design - Multiple tables into one foreign key column? @DrColossos That was actually the direction I was going with initially. This question was just out of my curiosity. I started to wonder how this would be achieved with just standard SQL (no triggers/stored procedures that are dependent on the specific RDBMS vendor). |
|
May 17 |
comment |
Relational Design - Multiple tables into one foreign key column? @DrColossos I thought a foreign key can only reference one table, though. |
|
May 17 |
awarded | Student |
|
May 17 |
asked | Relational Design - Multiple tables into one foreign key column? |
