正常化一个人的名字太远了？ [英] Is normalizing a person's name going too far?

问题描述

您通常规范化数据库，以避免数据冗余。在一个充满名字的表中很容易看到有大量的冗余。如果你的目标是创建一个地球上每个人的名字的目录（祝你好运），我可以看到如何规范化的名称可能是有益的。但在平均商业数据库的上下文中它是过度的？

（当然我知道你可以采取任何东西到极端...说如果你规范化到音节

更新：

一个可能的理由是随机名称生成器。

解决方案

数据库标准化通常是指对字段进行标准化，而不是对其进行标准化内容。换句话说，您将规范化在数据库中只有一个名字字段。这通常是值得的。然而，数据内容不应该规范化，因为它是个人的 - 你不是从列表中挑选，并且你不是在一个地方更改列表影响每个人 - 这将是一个错误，而不是一个功能。 / p>

You usually normalize a database to avoid data redundancy. It's easy to see in a table full of names that there is plenty of redundancy. If your goal is to create a catalog of the names of every person on the planet (good luck), I can see how normalizing names could be beneficial. But in the context of the average business database is it overkill?

(Of course I know you could take anything to an extreme... say if you normalized down to syllables... or even adjacent character pairs. I can't see a benefit in going that far)

Update:

One possible justification for this is a random name generator. That's all I could come up with off the top of my head.

解决方案

Database normalization usually refers to normalizing the field, not its content. In other words, you would normalize that there only be one first name field in the database. That is generally worthwhile. However the data content should not be normalized, since it is individual to that person - you are not picking from a list, and you are not changing a list in one place to affect everybody - that would be a bug, not a feature.

这篇关于正常化一个人的名字太远了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！