Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4901 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I'm trying to understand the proper use of optionality on potentially both sides of a relationship. Example:

Entity A has zero, one, or many entity Bs. I'm thinking this would be drawn as:

A --------o< B

... rather than:

A -o-|----o< B

... because the "o" on the right side fully explains that there may be no related items.

My hunch is also that the "|" on the left side, alone, would not be necessary, since an unadorned line on the left means 1:

A -|------o< B

I thought I'd ask here.

Bob

Posted

Entity A has zero, one, or many entity Bs.

This would be drawn as:

A ?? --------o< B

What to draw on the side closer to A depends on how many A's can a B have - and you haven't said anything about that.

Posted

0 or 1. I was thinking that:

A ---

... was a simplified way of describing that A cannot have many (that it would be 0, or 1). Would you then suggest this way of drawing it?:

A -|-o----o-< B

Thanks,

Bob

Posted

Yes. See also:

http://www2.cs.uregina.ca/~bernatja/crowsfoot.html

BTW, modality is less critical than cardinality, esp. if you are going to implement in Filemaker. IMHO, an ERD using only

A ----< B

notation to indicate a one-to-many is quite sufficient to convey the intended meaning.

Posted

BTW, modality is less critical than cardinality, esp. if you are going to implement in Filemaker. IMHO, an ERD using only

A ----< B

I just read that in the FM Training Series book. Thanks also for the url, very useful.

Bob

This topic is 4901 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.