>I'm not sure how to explain this. I have a parent-child relation, but there can be different types of children. I'm wondering if I should make a different child table for each type of child, or or try to homogonize them into one child with a field telling what type they are.
>
>Having different tables would be good because I need to store different data about different children. The problem is that if I need a new child type, I need a new table.
>
>Does this make any sense?

Yes. If the data are different and you create just 1 table, then you have to have fields for all the different data. So you would then have a bunch of blank fields. If you add another child type, then you get to modify the structure, unless you can have generic one-size-fits-all fields.

I think different tables would be easier to maintain and follow [with respect to development].