Jean-Luc Lachance schrieb:
> Do you really need MANY-TO-MANY between customers and projects?
> I can see customers owning many projects, but do you really have
> projects belonging to many customers?
In this case yes.
1, 'x-fair 2003';
2, 'y-fair 2003';
3, 'x-fair 2004')
1, 'X ltd';
maybe all 3 have a stall on project 1.
c1 and c2 attend project 2 where c2 has 2 stalls one inside and one
outside the hall.
I have the cust_project relation to tie other objects like proposals and
letters to something small and common for all the communication to a
> If not, fold cust_proj into projects.
> Otherwise, UNIQUE (cp_id, stall_no) on stalls should be enough.
cp_id implies uniquness of (customer, project) couples.
So with UNIQUE (cp_id, stall_no) we get
--> UNIQUE (c_id, p_id, stall_no)
This'd be too much. Stall_no is the number of the cubicles the customers
It needs to be unique within on project so that we can relate on a
specific spot on the area to send visitors when they ask us and we print
those numbers in the flyer.
In response to
pgsql-sql by date
|Next:||From: Andreas||Date: 2004-05-27 07:22:53|
|Subject: Re: Multitable uniqueness ?|
|Previous:||From: sad||Date: 2004-05-27 03:56:19|
|Subject: Re: The PostgreSQL|