Array columns vs normalized table - Mailing list pgsql-general

From Lee Hachadoorian
Subject Array columns vs normalized table
Date
Msg-id 5ab13581003020921q3b5dd481mf118fa05f555fd7b@mail.gmail.com
Whole thread Raw
Responses Re: Array columns vs normalized table
Re: Array columns vs normalized table
Re: Array columns vs normalized table
List pgsql-general
I work with state labor data which is reported to us in the form

    industry, year, quarter1, quarter2, quarter3, quarter4

where each quarter represents an employment count. Obviously, this can
be normalized to

    industry, year, quarter, employment

Can anyone comment on, or point to me to an article or discussion
regarding, why one would use an array column instead of normalizing
the data? That is, would there be any benefit to storing it as

    industry int, year smallint, employment int[ ]

where the last column would be a four element array with data for the
four quarters.

Thanks,
--Lee

--
Lee Hachadoorian
PhD Student, Geography
Program in Earth & Environmental Sciences
CUNY Graduate Center

pgsql-general by date:

Previous
From: Scott Bailey
Date:
Subject: Re: to_timestamp() and quarters
Next
From: Vick Khera
Date:
Subject: disable triggers isolated to transaction only?