From: | Alexandre Leclerc <alexandre(dot)leclerc(at)gmail(dot)com> |
---|---|
To: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
Cc: | PERFORM <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Flattening a kind of 'dynamic' table |
Date: | 2005-01-27 17:43:56 |
Message-ID: | 1dc7f0e30501270943683ced12@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 27 Jan 2005 17:27:40 +0100, Dawid Kuroczko <qnex42(at)gmail(dot)com> wrote:
> On Thu, 27 Jan 2005 10:23:34 -0500, Alexandre Leclerc
> <alexandre(dot)leclerc(at)gmail(dot)com> 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?
Regards.
--
Alexandre Leclerc
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-01-27 18:02:48 | Re: Flattening a kind of 'dynamic' table |
Previous Message | Alexandre Leclerc | 2005-01-27 17:43:25 | Re: Flattening a kind of 'dynamic' table |