Skip site navigation (1) Skip section navigation (2)

Database Structure

From: "Chad Thompson" <chad(at)weblinkservices(dot)com>
To: "pgsql-novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Database Structure
Date: 2002-08-07 15:31:37
Message-ID: 047601c23e27$854d2f70$32021aac@chad (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
I have what should be a very dumb problem, but i keep questioning myself on the best way to fix it.  So i thought id throw it out to y'all and see what comes back. 

I have 3 tables.  Clients, Projects, and Lists.  There is a one to many relation between Clients and Projects, and Clients and Lists.
That is to say that a client can have multiple projects and these projects can use any or all of his lists.

This works fine, the wrinkle comes in when i have a client, who has clients who have their own lists.  
I treat this just as a client with different projects, but the lists now need to be associated with this project only, and no longer with every project that this client has.

Should I create another table to handle these exceptions? or is there a more elegant way.



pgsql-novice by date

Next:From: RobinDate: 2002-08-07 16:47:20
Subject: Locked out of postgres on my redhat 7.3
Previous:From: Oliver ElphickDate: 2002-08-07 15:31:11
Subject: Re: UPDATE across tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group