Re: [GENEAL] dynamically changing table - Mailing list pgsql-general

From A B
Subject Re: [GENEAL] dynamically changing table
Date
Msg-id dbbf25900903301150y724e55e4s9d35123ed5c87df9@mail.gmail.com
Whole thread Raw
In response to Re: [GENEAL] dynamically changing table  (David Fetter <david@fetter.org>)
Responses Re: [GENEAL] dynamically changing table  (Andrej <andrej.groups@gmail.com>)
Re: [GENEAL] dynamically changing table  (Sam Mason <sam@samason.me.uk>)
Re: [GENEAL] dynamically changing table  ("Will Rutherdale (rutherw)" <rutherw@cisco.com>)
List pgsql-general
2009/3/30 David Fetter <david@fetter.org>:
> On Mon, Mar 30, 2009 at 05:39:19PM +0200, 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.
>
> Stop right there.  You need to get some sanity into your project,
> either by changing that requirement, or by not using an RDBMS for it.
>
> Cheers,
> David.


Well, the requirement is: keep a lot of data stored, don't loose any
of it, and you will not know what you will have to store (changing
number of fields and of different types)
But it is not all that bad, the fields will be integers, or text, or
floatingpoint numbers.

One  option is, put it in a db as a huge text  (or in textfiles, one
per object) and parse it when you need it. That might also work.

Why are you demanding sanity? I need crazy ideas to get this to work ;-)

pgsql-general by date:

Previous
From: Jennifer Trey
Date:
Subject: Re: PostgreSql with or without Plus?
Next
From: Steve Crawford
Date:
Subject: string_to_array with empty input