Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Framework - resolving ambiguous relationships

Status
Not open for further replies.

fmwannabe

IS-IT--Management
Jun 30, 2008
3
US
Framework manager models are usually set up with 3 namespaces - one for imported data sources, one for working, and one for business presentation.

We also learned that the imported namespace should be kept as close to the source as possible, except for relationships.

My question is about resolving ambiguous relationships. Is it best to create query subject roles and resolve the relationships in the data source namespace or the working namespace?

Thanks.
 
The namespace that holds the database objects may contain all sorts of ambiguous relationships as it is dictated by the source relationships. The second layer should be responsible for creating the proper star-models (and hence contain no ambiguouty at all)
In the end the model will dictate the join strategy between the model query subjects. (which you name as query subject roles)

Ties Blom

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top