New answers tagged database-structure
If I were you, I would generalize the design, I.e. instead of a motorcycle_brand table, You would want a category_brand table, and instead of a motorcycle_model table, you would have a category_brand_model table with an fk on the category_brand pk. This allows for several advantages: Adding new product categories in the future requires only adding records, ...
Well , i would add a new column on the Statistics_Entry as your year column ! Next depending on the volume of your data i would partition that table using this column(this will speedup your query when using the year column as your predicate). This lookup table can be a view ! I would not create a new table just for the year column, this would just make ...
I would consider removing to a separate table the position and dates of position. Tables ------ Person Country Person_Role FK to Person, listing all current and previous positions Current_Leader FK to Person and Country (may or may not want to have this)
Assuming that: every country has at most 1 leader in a given point in time (no overlaps). there may be gaps in a country's leadership (if you don't want to allow that, change the scond constraint to prevtermend = termstart) termstart < termend, i.e. every term lasts at least 1 day (if that is not the case, you can alter the constraints below, either by ...
Top 50 recent answers are included