Let's say that I have 30 tables in my database which all have a one-to-many relationship to a `Notations` table:

What is another way to set up the `Notations` table (other than containing a foreign key column for each of its "parents") that would be less taxing to the query's performance? The table is expected to grow to be very large.

(As each Notation contains a single parent\_table\_id with 29 null values for the remaining parent\_tables - that is 29 nulls to track for every row, it seems like a lot)

ie.
`SELECT text, table1_id, table2_id, ..., table30_id FROM Notations` would show:

```
id         text         table1_id       table2_id      //     table30_id
0          "buzz"       74              null           //     null
1          "foo"        null            45             //     null
2          "bar"        22              null           //     null
3          "fizz"       22              null           //     null
4          "hello"      28              null           //     null
5          "world"      null            null           //     3
...etc

```