Re: Database design pattern question

This design fallacy is called attribute splitting. You are putting
things that belong to one entity split over multiple tables.

Temporal things are stored with a (start, end) timestamp pair. They
have durations and are not points in time. You can get the details at
University of Arizona's website -- look up Rick Snodgrass and download
his book.

Next,the ISO sex code is 0= unknown, 1= male, 2= female 3= lawful
person (corporations). ths means you always have a code for sex and
zero is the default
value.

You can do the same thing with title.

Next, you need better names that actually tell us what the data
elements are; does sex mean "sex_code" or "sex_frequency" ?

.

Relevant Pages