In article <437FAA9F-DF2D-429E-9856-EB2026B55940@solfertje.student.utwente.nl>,
Alban Hertroys <dalroi@solfertje.student.utwente.nl> writes:
> On Mar 30, 2009, at 5:39 PM, A B wrote:
>> Hi,
>> In the next project I'm going to have a number of colums in my tables,
>> but I don't know how many, they change. They all use integers as
>> datatype though.. One day, I get 2 new columns, a week later I loose
>> one column, and so on in a random pattern.
> Ignoring design implications (you got enough replies about that I
> think)...
> You could add the columns you're sure that you need and put the rest
> in an XML field.
<mantra>
If you have a problem and want to solve it using XML, you have two problems.
</mantra>
Why serializing the rest of the data in an XML field? contrib/hstore
seems to accomplish the same, without the XML overhead.