David Fetter escribió: > On Tue, Oct 27, 2009 at 09:13:29PM -0400, Tom Lane wrote: > > Robert Haas <robertmh...@gmail.com> writes: > > > I confess that I'm a bit mystified about the design of the > > > reloptions stuff. It seems kind of odd to store structured data as > > > text[]; it's kind of the opposite of what I would normally > > > recommend as good database design. > > > > It's definitely a bit EAV-ish :-(. But I don't see any particularly > > easy way to modify it to store bool/int/float parameters in their > > native types; do you? > > More columns, each of the correct type, with the table constraint that > at most one may be populated is how I handle stuff like that.
So we would have "spcintoptions", "spcfloatoptions", and so on? (I don't see the need for the table constraint in this case.) -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
