normalization review

#1

What normal form is violated here?
What could fix the problem?

A telephone call is uniquely identified by telephone number and time of call.
These candidate keys compose the composite primary key. There is another
attribute/column “telephone location”.

telephone number | time of call | telephone location(precise)

#2

landonkelsey wrote:

Quote:

What normal form is violated here?
What could fix the problem?

A telephone call is uniquely identified by telephone number and time ofcall.
These candidate keys compose the composite primary key. There is another
attribute/column “telephone location”.

telephone number | time of call | telephone location(precise)

Good luck with the homework assignment!

#3

I am semi-retired at the age of 67!

Not a homework assignment!

I have the answer if you'd like to hear it!

Bob Badour wrote:

Quote:

What normal form is violated here?
What could fix the problem?
[quoted text clipped - 4 lines]

telephone number | time of call | telephone location(precise)

Good luck with the homework assignment!

#4

"landonkelsey" <u36972@uwe> wrote

Quote:

What normal form is violated here?
What could fix the problem?

A telephone call is uniquely identified by telephone number and time of
call.
These candidate keys compose the composite primary key. There is another
attribute/column "telephone location".

telephone number | time of call | telephone location(precise)

No form is violated.

#5

2 is violated ...why?

Evan Keel wrote:

Quote:

What normal form is violated here?
What could fix the problem?
[quoted text clipped - 4 lines]

telephone number | time of call | telephone location(precise)

No form is violated.

#6

landonkelsey wrote:

Quote:

I am semi-retired at the age of 67!

Not a homework assignment!

So where are you doing it then?

just kidding,
p

#7

location depends only on the telephone number not on the entire primary key

However if the telephone were a cellphone, there would be no violation!

Look at the Boyce Codd normalization principle

landonkelsey wrote:

Quote:

2 is violated ...why?

What normal form is violated here?
What could fix the problem?
[quoted text clipped - 3 lines]

No form is violated.

#8

"landonkelsey" <u36972@uwe> wrote

Quote:

2 is violated ...why?

Why?

Quote:

Evan Keel wrote:
What normal form is violated here?
What could fix the problem?
[quoted text clipped - 4 lines]

telephone number | time of call | telephone location(precise)

No form is violated.

#9

landonkelsey wrote:

Quote:

2 is violated ...why?

Because you have made up a set of FD's whereby it violates 2nf.

Quote:

Evan Keel wrote:

What normal form is violated here?
What could fix the problem?

[quoted text clipped - 4 lines]

telephone number | time of call | telephone location(precise)

No form is violated.

#10

landonkelsey wrote:

Quote:

location depends only on the telephone number not on the entire primary key

However if the telephone were a cellphone, there would be no violation!

Look at the Boyce Codd normalization principle

Without having ever specified a PK, the above doesn't make much sense.

Location does not depend on the phone number in many offices with PBX
systems. Any phone can make and receive calls on any line.

Quote:

landonkelsey wrote:

2 is violated ...why?

What normal form is violated here?
What could fix the problem?

[quoted text clipped - 3 lines]

No form is violated.