4 Tag; formatting; etc.
source | link

I have the following STUDENT relation in first normal form, where id has been identified as the primary key (email here is also unique for all tuples):

STUDENT(id, email, first_name, last_name)

I want to normalize this relation/table such that it is in third normal form (3NF).

The dependencies that I've been able to identify from the above STUDENT relation/table are the following

Full:

{ id ->} → { email }

Transitive:

{ email ->} → { first_name, last_name }

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PKprimary key (id), and the attribute/column email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventualeventually get to a third normal form3NF which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT tablerelation/table here seems very redundant, as all it does is point to another tablerelation/table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial tablerelation/table has two candidate keys which both could either be the primary key (id or email both could uniquely identify each row).

I have the following STUDENT relation in first normal form, where id has been identified as the primary key (email here is also unique for all tuples):

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

I have the following STUDENT relation in first normal form, where id has been identified as the primary key (email here is also unique for all tuples):

STUDENT(id, email, first_name, last_name)

I want to normalize this relation/table such that it is in third normal form (3NF).

The dependencies that I've been able to identify from the above STUDENT relation/table are the following

Full:

{ id } → { email }

Transitive:

{ email } → { first_name, last_name }

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the primary key (id), and the attribute/column email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventually get to a 3NF which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT relation/table here seems very redundant, as all it does is point to another relation/table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial relation/table has two candidate keys which both could either be the primary key (id or email both could uniquely identify each row).

3 added 45 characters in body
source | link

I have the following STUDENT relation in first normal form, where id has been identified as the primary key (email here is also unique for all tuples):

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

I have the following STUDENT relation in first normal form, where id has been identified as the primary key:

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

I have the following STUDENT relation in first normal form, where id has been identified as the primary key (email here is also unique for all tuples):

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

STUDENT(id, email)
STUDENT_INFO(email, first_name, last_name)

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

2 added 59 characters in body
source | link

I have the following STUDENT relation in first normal form, where id has been identified as the primary key:

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

 
STUDENT(idid, email)

  
STUDENT_INFO(emailemail, first_name, last_name)
  

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

I have the following STUDENT relation in first normal form, where id has been identified as the primary key:

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

STUDENT(id, email)

 STUDENT_INFO(email, first_name, last_name)
 

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

I have the following STUDENT relation in first normal form, where id has been identified as the primary key:

STUDENT(id, email, first_name, last_name)

I want to normalize this relation such that it is in third normal form.

The dependencies that I've been able to identify from the above STUDENT relation are the following

Full:

id -> email

Transitive:

email -> first_name, last_name 

Here's the part where I'm confused. I've identified email as a transitive dependency as it can be identified by the PK (id), and the attribute email itself can identify and determine the first_name and last_name.

...if I was to continue with this idea, I would eventual get to a third normal form which looks like so:

 
STUDENT(id, email) 
STUDENT_INFO(email, first_name, last_name) 

However, the STUDENT table here seems very redundant as all it does is point to another table. Is my normalization process here correct? Or did I get my dependencies wrong? It seems that I will always run into this problem whenever the initial table has two keys which both could either be the primary key (id or email both could uniquely identify each row)

1
source | link