Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Le 1 nov. 2009 à 13:43, Greg Stark <gsstark(at)mit(dot)edu> a écrit :
>>> We could have a column for all booleans, a column for all integers,
>>> etc. but that's not really any more normalized than having a single
>>> column for all the types with a rule for how to marshal each value
>> Thé other day, on IRC, someone wanted a dynamic table accepting value in
>> whichever column you name. That would probably mean having a special INSERT
>> INTO which ALTER TABLE ... ADD COLUMN ... for you.
>> Maybe INSERT INTO ... WITH ADD COLUMN OPTION;
>> This sure looks suspicious, but the asking came from another product and it
>> seems that could help here too. Oh and you get text columns I guess, by
> If you want to start a discussion about a topic that is completely
> unrelated to this one, then please start a new thread.
Auto adding a column on INSERT when it does not exists would help tools
to add columns in there, to avoid having to follow EAV model.
Maybe this property would be tied to the table rather than the INSERT,
though, or maybe we'd be better without it at all. But it's related to
the case at hand, yes.
PostgreSQL DBA, Architecte
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2009-11-03 12:49:34|
|Subject: Re: per-tablespace random_page_cost/seq_page_cost|
|Previous:||From: Peter Eisentraut||Date: 2009-11-03 11:31:14|
|Subject: Re: new version of PQconnectdb was:(Re: [HACKERS]
Determining client_encoding from client locale)|