Skip to main content
added 197 characters in body
Source Link

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity, or should you introduce a new sub-type or referenced entity to the model.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

So the model evolves from a single table into a proper model, eg:

Symbol
  AlphabetSymbol
Alphabet
SybolLooksLikeSymbol
Shape
SymbolLooksLikeShape
SymbolUpperCaseOfSymbol

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity, or should you introduce a new sub-type or referenced entity to the model.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity, or should you introduce a new sub-type or referenced entity to the model.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

So the model evolves from a single table into a proper model, eg:

Symbol
  AlphabetSymbol
Alphabet
SybolLooksLikeSymbol
Shape
SymbolLooksLikeShape
SymbolUpperCaseOfSymbol
added 74 characters in body
Source Link

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity, or should you introduce a new sub-type or referenced entity to the model.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity, or should you introduce a new sub-type or referenced entity to the model.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.

Source Link

In general you resist adding so many attributes to the model, and normalize the model. For each attribute ask 1) is it really necessary to add to your data model, and 2) does it really belong as an attribute of this entity.

Eg is_rtl probably should be an attribute of a related Alphabet entity, looks_like_d should be modeled in a seperate linking table, and is_shaded_triangle_like is probably not worth adding to the data model.