Correct! :-) Flattening would only be useful if you wanted to logically have the relationship:
Quote <<--->> Product Since there is actual information in the QuotedProduct join table, you don’t want to flatten. Regards, Mark On Oct 20, 2014, at 2:41 PM, Flavio Donadio <fla...@donadio.com.br> wrote: > Hello, people! > > > I am experimenting a little more... and hitting some roadblocks! > > Example: I have these entities called Product and Quote. A Quote has many > products. But each quoted product has more information, like price, quantity > and lead time. So, I am using this QuotedProduct entity, which "binds" the > Product id, the Quote id and the other information. > > The relationship could be expressed like this: > > Quote <--->> QuotedProduct <<---> Product > > I understand I shouldn't flatten any of these relationships. Am I right? > > > Cheers, > Flavio > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/mark.morris%40experian.com > > This email sent to mark.mor...@experian.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
