As i undestand it: If I do it bidirectional in my example i would insert a row pr. mailmessage for each user i sent it to, it would gime a lot of similar mailmessages, with just the toUsers field changed, if you have a unidirectional relation with a relation table you would only have one row in mailmessages with the actual message and a lot of foreign key in the relation table thar points at this one message. so you would not have a lot of unnessesary data, and the database woulnd grow as big. Im not a pro database, but i would think it would give me some performance, if i just have a relation table which only contains keys to my actual tables.
Regards, David On Thu, 2003-10-02 at 12:30, Daniel L�pez 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
