Re^3: OT: benefits of database normalization

My understanding was based on the name of the columns: "type". I don't deny that there is a chance of misunderstanding. Column type might mean something that really not sort of "type". To really appreciate whether design 1 is actually normalized, I have to judge base on the meaning of the true data, which you didn't really specify in your original post. (It would be much easy if we are in front of a whiteboard now ;-).

To clarify, what I meant was: (I have to use something that is more meaningful to everyone, something that is part of everyone's daily life, and yet describes my understanding of your design 1. ProductOf is my understanding of your "type".)

Fruit	ProductOf	Taste
Apple1	1	Some Taste
Apple2	2	Some Taste
Orange1	1	Some Taste

country code	country name
1	US
2	Canada

This is normalized, but will be not normalized, if:

Fruit	ProductOf	country name	Taste
Apple1	1	US	Some Taste
Apple2	2	Canada	Some Taste
Orange1	1	US	Some Taste

Comment on Re^3: OT: benefits of database normalization

Replies are listed 'Best First'.
Re^4: OT: benefits of database normalization by revdiablo (Prior) on Oct 03, 2004 at 02:59 UTC
My understanding was based on the name of the columns. I thought they would be self-evident, but on reflection, I probably should not have assumed as much. I have a bad habit of doing this. I just get wrapped up in the problem, and don't think about it from an outside perspective. I have updated the original post. Hopefully the further explanation is helpful. To clarify, what I meant was . . . Indeed, this appears to be a nicely normalized design. I can understand what you were thinking when looking at my bad examples. This isn't quite the situation I was discussing, though. I hinted at that when I said The data column's meaning changes depending on the value of the type column, but I can see how my post could have been misunderstood. Let me know if the update explains things better, or if there is still something missing.	[reply]

Replies are listed 'Best First'.

Re^4: OT: benefits of database normalization
by revdiablo (Prior) on Oct 03, 2004 at 02:59 UTC

My understanding was based on the name of the columns.

I thought they would be self-evident, but on reflection, I probably should not have assumed as much. I have a bad habit of doing this. I just get wrapped up in the problem, and don't think about it from an outside perspective. I have updated the original post. Hopefully the further explanation is helpful.

To clarify, what I meant was . . .

Indeed, this appears to be a nicely normalized design. I can understand what you were thinking when looking at my bad examples. This isn't quite the situation I was discussing, though. I hinted at that when I said The data column's meaning changes depending on the value of the type column, but I can see how my post could have been misunderstood. Let me know if the update explains things better, or if there is still something missing.

[reply]