Let's say my source data set has a characteristics table attached to my primary table; i.e.,
person == primary table with person identifier, name.
person_phone == one to many relationship based on person id with columns like 'phone_type' and 'phone', so if the system understood I had a home and a cell phone, I'd have two rows in this table.
Now, let's further say that my destination table just wants to have a structure like this:
personId
cellPhone
homePhone
Running a blanket query against my characterstic table and joining created too many rows if I had more than one row in person_phone.
I've been able to craft something that touches the same source one-to-many table (i.e., phone) and incorporates in formulas along the path to get there, but it seems clunky as anything and I really only cared about cellular and phone. It occurs to me that if I had a lot of different values to access via descriptor I'd wind up querying the same table N times.
I'm thinking that I'm missing something pretty easy here.
Any insight is appreciated.
Thanks.
brian