X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 63A613A621A for ; Fri, 28 Jan 2005 08:08:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20596-06 for ; Fri, 28 Jan 2005 08:08:00 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by svr1.postgresql.org (Postfix) with ESMTP id 7067F3A620D for ; Fri, 28 Jan 2005 08:08:00 +0000 (GMT) Received: by rproxy.gmail.com with SMTP id z35so383182rne for ; Fri, 28 Jan 2005 00:08:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=UANjU94SOvGQvIcYaEbG4PsKtwOtAj3YLc6J0hHNa2u28crvUXFsLTWAZI1D8NBr/9+prb51odm86GTAKO9S5ZwaYyRz9WOcKmDnvDSdGPHROHvDgxk/0huUeV53RozVz/qD5jnHSxh69Kdl8ctWzMZjTFtC/FS8ebiQbZMRVbM= Received: by 10.38.209.66 with SMTP id h66mr63678rng; Fri, 28 Jan 2005 00:07:59 -0800 (PST) Received: by 10.38.163.47 with HTTP; Fri, 28 Jan 2005 00:07:59 -0800 (PST) Message-ID: <758d5e7f050128000716f28a59@mail.gmail.com> Date: Fri, 28 Jan 2005 09:07:59 +0100 From: Dawid Kuroczko Reply-To: Dawid Kuroczko To: Alexandre Leclerc Subject: Re: Flattening a kind of 'dynamic' table Cc: PERFORM In-Reply-To: <1dc7f0e30501270943683ced12@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1dc7f0e305012707234159cfc8@mail.gmail.com> <758d5e7f050127082755f9af12@mail.gmail.com> <1dc7f0e30501270943683ced12@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.548 tagged_above=0 required=5 tests=AWL, FROM_ENDS_IN_NUMS, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200501/567 X-Sequence-Number: 10257 On Thu, 27 Jan 2005 12:43:56 -0500, Alexandre Leclerc wrote: > On Thu, 27 Jan 2005 17:27:40 +0100, Dawid Kuroczko wrote: > > On Thu, 27 Jan 2005 10:23:34 -0500, Alexandre Leclerc > > wrote: > > > Here a normal listing of design.product_department_time: > > > product_id | department_id | req_time > > > ------------+---------------+---------- > > > 906 | A | 3000 > > > 906 | C | 3000 > > > 906 | D | 1935 > > > 907 | A | 1500 > > > 907 | C | 1500 > > > 907 | D | 4575 > > > 924 | A | 6000 > > > 924 | C | 1575 > > > > Well, I did something like this recently; it can be done though > > maybe not very efficiently... > > > > Unfortunately we will need a rowtype with all the departaments: > > CREATE DOMAIN departaments AS (a int, b int, c int, d int, ...); > Thank you for this help Dawid, I'll have to take some time to look at > this suggestion. If I must create a domain with all the departments > I'll have a problem because the user is creating and deleting > departments as it pleases him. > > Any counter-ideas? I have exactly the same problem with my proposal [1] I just wish there would be some "native" rows-to-columns aggregate. The other approach I used was something like this: SELECT product_id, a, b, c FROM (SELECT product_id, a FROM pdt) AS a FULL OUTER JOIN USING(product_id) (SELECT product_id, b FROM pdt) AS b FULL OUTER JOIN USING(product_id) (SELECT product_id, c FROM pdt) AS c; ...or similar (I'm typing from memory ;)). Anyway it was good for getting whole table, but performance well, wasn't the gratest. ;)). Regards, Dawid [1]: I was thinking about a trigger on a "departaments" table, and then recreating the aggregate and view as needed, but it isn't the kind of dynamic I had in mind. ;)