After further though, I tried using a function: CREATE OR REPLACE FUNCTION children ( ow integer, parent text) returns integer AS $$ select count(*) as children from m where o = $1 and name ilike $2 || '/%'; $$ LANGUAGE sql;
An example call is: select o, name, f1, f2, (select children(o,name) as children) from m where o=3; Which worked, but was no faster than selecting all of the matching ids and iterating through them on the client finding each row's parent count each in its own select. Ie, it took about 1 ks for about 20k rows. So it looks like the real solution is to add a column to track the number of children and update it, for each "parent" row via a trigger whenever a row is added, removed or the path column of a row is changed. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6 -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
