Welcome to dbFreaks.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Are circular relationships a bad thing in ER-modeling?

 
   Database Help (Home) -> Object-Oriented RSS
Next:  ECOOP 2004; European Conference on Object-Oriente..  
Author Message
xlazyx

External


Since: May 03, 2004
Posts: 1



(Msg. 1) Posted: Mon May 03, 2004 6:22 pm
Post subject: Are circular relationships a bad thing in ER-modeling?
Archived from groups: comp>databases>object (more info?)

Hey!

If I have the following theatre system:

A theater sets up _shows_, which is based on a _manuscipt/play_ written by a
_person_ A show also has _persons_in differnent _roles_, based on the
_manuscript_.

And have the following entities:

Theater(TheaterID, Name)
Manuscript(ManuscriptID, Name, Year)
Person(PersonID, Name)
Show(ShowID, ManuscriptID, TheaterID, Date, Time)
Role(RoleID, ManuscriptID, Name)

How do I relate a Person to a show, so that a person can be an actor in a
show, in multiple roles?

And how do I relate a Person to a Manuscript, so that many people can write
the same manuscript, and one person can write serveral manuscripts.

As I see it I would end up with something like:

Person->Show->Manuscript->Person, which is a circle relationship. Isn't this
bad? Or is it ok?

Of course, there has to be an entity between Person and Show because of the
N:N relationship, but that's not a problem right?

Thanks for any input on this!!

Tor Arne

 >> Stay informed about: Are circular relationships a bad thing in ER-modeling? 
Back to top
Login to vote
Display posts from previous:   
   Database Help (Home) -> Object-Oriented All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]