Because if it's bidirectional, 1 project has many requirements for example, then you store the project PK in the associated requirement table as a foreign key. If it's unidirectional then you can't store the Project pk in the requirement table. Strictly speaking 1 to many, and many to many, unidirectional are actually <undefined> to many.
On 2/10/03 11:30 am, "Daniel L�pez" <[EMAIL PROTECTED]> wrote: > Hi, > Do you really need an extra table when creating a unidirectional 1-n > relationship? I've always used bidirectional relationships so I've never > tried, but I don't see the reason why unidirectional ones would require > such an extra table. May be I did not understand the statement below. > Cheers, > D. > > Edward Kenworthy escribi�: >> This is a unidirectional 1:m so yes you do need a relationship table. > ... //snipped > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
