On Sun, Feb 03, 2008 at 10:00:04PM +0100, dfx wrote: > Yes, this is the "normal" way, but I was tempted to investigate the > possibility to use array (of string) or composite types to avoid to > increase the number of tables That is an extremely bad thing to "optimize" for. Add tables as needed for your data. > and to simplify stored procedures reducing the number of join. That's a bad thing to "optimize" for, too. Just do your JOINs, and *if* you discover a performance problem, come back here and get help on it. > Thi idea was born following the discussion concerning EAV. EAV is just a mistake. Cheers, David. -- David Fetter <david@xxxxxxxxxx> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@xxxxxxxxx Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
