Results 1 to 2 of 2

Thread: Normalizing Database

  1. #1
    Join Date
    Mar 2007
    Posts
    3

    Normalizing Database

    Hello Everyone,

    I have a design problem that maybe someone could help me with. I am refactoring an old table of mine that was developed long ago, before I knew anything about normalization.

    The table is very simple. It is called population projections. The current schema is:

    id, projection_year, year_round (population), seasonal

    I'm trying to decide if it is better to break out the year_round from the seasonal and have two records with a type field, like:

    id, projection_year, type, population

    1, 2020, Year-Round, 23000
    2, 2020, Seasonal, 42000

    Anyone have any suggestions?

    Thanks,
    Lee

  2. #2
    Join Date
    Mar 2007
    Posts
    16
    Looking at what you have presented I would say absolutely not.
    I'm guessing these projections relate to some other table? like a country table, so england (year_round = 23000, seasonal = 42000). Unless there are several seasonal figures for each year_round figure (during 2020) then there is no point in dividing them up. Better to use two columns as in your original design.

    Ideally it would be helpful to know what the ID column relates to.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •