2009/6/16 A B <gentosaker@xxxxxxxxx>: > > 2009/6/16 Greg Stark <gsstark@xxxxxxx> >> >> I don't think think it's fair to call this EAV actually. It sounds >> like the integers are a collection of things which represent the same >> thing. Ie, they're all bank balances or all distances driven, just for >> different time periods. Storing all objects representing the same >> thing in the same column is just a regular normalized table, not EAV. >> >> You might want to consider partitioning the table of integers by type >> to facilitate dropping the old ones. But that's an administrative >> trick, not a fundamental schema design decision. > > Unfortunatly there is no "type" here. One can make no distinction between > the integers and one can not tell when they are added or dropped. > Or did I misunderstand you Greg? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
