Re: How to work with m:n relationships?

vldm10 wrote:
> As previous discussants in this thread (Leffler and Portas) didn't
> presented the solution which they prefer (the current solutions in RM
> like [TDRM] and similar), let me make a very short analysis of this
> kind of the solutions.
> Using example from this thread the current RM's solutions will assign
> following key for the relation Subscriber: Primary Key (ssn, mm, dd,
> yy, hh, mm, ss), that is 7 attributes. Similarly for the Relation
> Product: Primary Key (product_code, mm1, dd1, yy1, hh1, mm1, ss1) that
> is 7 attributes.
> Join relation SubscriberProduct will have 20 attributes. This is just
> very short analysis and the application is not to much complicate.
> In my solution Key has one attribute.
>
> Vladimir Odrljin

I originally thought you had something to say about RM. I now understand that this is purely about design. As with any design problem it can be difficult in an online discussion to define enough context to decide whether one solution should be preferred over another. I really don't understand what your example has that is new.

> Primary Key (product_code, mm1, dd1, yy1, hh1, mm1, ss1) that
> is 7 attributes.

Primary Key (product_code, date_time_stamp). That is 2 attributes. Your point is?

--
David Portas