Search Postgresql Archives

drawback of array vs join

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've a temporary table where I'd like to resume data coming from
several other tables (normalised the usual way).
eg.
a list of items that may belong to several group (eg. item,
group, itemgroup table) will end up in something similar to:

create temp table itemlisttemp(
  lid int,
  iid int,
  qty int,
  famid int,
  rating int,
  itemgroups int[],
);

This because I've to loop over the same table several times and
because it *should* make easier to write dynamic queries [built from
a web interface] like

select sum(qty) from where
  famid=3
  and rating>0
  and 10 = any itemgroups
...

itemlisttemp tables will be very small (30 as an upper limit) and
arrays as well will contain very few elements (4 as an upper limit).

I'm aware of the drawback of de-normalization.

Should I be aware of anything else when using arrays this way?

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux