Skip to main content
Database Administrators

Return to Question

Converted image links to inline display, fixed a typo
Source Link
edit approved May 14, 2021 at 19:14
user229856
edit approved May 14, 2021 at 19:14
user229856
  • 186
  • 1
  • 4

What I want to create is a table in a database for employees in a company.

Each employee has a unique identifier ID and a name. Each employee also has a list of skills, the skills are represented as a string (i.e. "Cashier", "Manager", etc.).

Multiple employees can have the same skill, for example, John is a Cashier and a Manager and Bob is also a Cashier.

I thought of two ways to represent this using an ERD:

  1. Using a multi valued attribute connected to the Employee entity: https://i.sstatic.net/bioKt.png

  2. Using a weak entity with the following cardinalities: https://i.sstatic.net/NDoid.png

    Using a multi valued attribute connected to the Employee entity:

multi valued attribute

  1. Using a weak entity with the following cardinalities:

weak entity

What i'mI'm asking is, are these two implementations the same, cardinality and all?

What I want to create is a table in a database for employees in a company.

Each employee has a unique identifier ID and a name. Each employee also has a list of skills, the skills are represented as a string (i.e. "Cashier", "Manager", etc.).

Multiple employees can have the same skill, for example, John is a Cashier and a Manager and Bob is also a Cashier.

I thought of two ways to represent this using an ERD:

  1. Using a multi valued attribute connected to the Employee entity: https://i.sstatic.net/bioKt.png

  2. Using a weak entity with the following cardinalities: https://i.sstatic.net/NDoid.png

What i'm asking is, are these two implementations the same, cardinality and all?

What I want to create is a table in a database for employees in a company.

Each employee has a unique identifier ID and a name. Each employee also has a list of skills, the skills are represented as a string (i.e. "Cashier", "Manager", etc.).

Multiple employees can have the same skill, for example, John is a Cashier and a Manager and Bob is also a Cashier.

I thought of two ways to represent this using an ERD:

  1. Using a multi valued attribute connected to the Employee entity:

multi valued attribute

  1. Using a weak entity with the following cardinalities:

weak entity

What I'm asking is, are these two implementations the same, cardinality and all?

Post Migrated Here from stackoverflow.com (revisions)
Source Link
Squidward_Dabbing
Squidward_Dabbing

Are these two ERDs the same? Do they represent the same thing? [Weak entities and multi-valued attributes]

What I want to create is a table in a database for employees in a company.

Each employee has a unique identifier ID and a name. Each employee also has a list of skills, the skills are represented as a string (i.e. "Cashier", "Manager", etc.).

Multiple employees can have the same skill, for example, John is a Cashier and a Manager and Bob is also a Cashier.

I thought of two ways to represent this using an ERD:

  1. Using a multi valued attribute connected to the Employee entity: https://i.sstatic.net/bioKt.png

  2. Using a weak entity with the following cardinalities: https://i.sstatic.net/NDoid.png

What i'm asking is, are these two implementations the same, cardinality and all?