July 6, 2005 at 2:47 pm
Why is a calculated column not a normalization issue?
July 6, 2005 at 2:49 pm
What is the underlying question??
July 6, 2005 at 2:56 pm
All columns must be dependent on the primary key. If it is a calculated column it will be dependent on the columns involved in the calculation. From what i understand that violates what 3NF.
July 6, 2005 at 3:02 pm
Would love to hear Joe Celko's comment on this topic... I can't really answer this one as design is not my specialty. I would think that a computed column can beneficial sometimes but that this work should be done in the front end most of the time, therefore its rightfull place would not be on the server (normalized version).
July 6, 2005 at 3:50 pm
Well I am not Joe Celko but I can tell you that a calculated column is not STORED in the table it is just a comodity for implementation!
Reality is also that if you create an index on it you are materializing the values in the index but that is a different story
* Noel
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply