Do i need 3 different tables to accomplish this?

Hi folks,
This is my first post on the SQL forum and maybe it's a dummy question but... i didn't figure it out.
Also, i'm not sure if it's the right place for this type of questions, excuse me if i'm on the wrong spot.

Here we go: I'd like to have on my web sites some articles and bellow each article a list of "Related Articles".
I started with something like this:

After that, i noticed that i have an "One to Many" relationship between the 2 tables (fields ArticleID) but, if i try to create another relationship likeArticleRelated.ArtigleRelatedID -> Articles.ArticleIDit will looks like a circle between the 2 tables and i'm not sure if it's the best way (even if it will work).

Before somebody ask "Wy do i need this third relationship", besides other good reasons, i'm using "LINQ To SQL" and i just drag and drop the tables to the designer window and it automatically create classes and colections based on the existent relationship.

I appreciate any help.

It is a general principle of database design that wherever possible all relationships should be constrained at the database level. Therefore I suggest that you do define the second relationship. I have just set up two tables as you have done. When I added the second relationship, I ended up with a second copy of Articles on the relationship diagram. I suggest that you try again to create the second relationship.

|||

thanks a lot