Hi,
It seems there's something wrong in the design of your db : Don't you have
another table containing name attribute as primary key which you could refer
as foreign key in staf_xxxx ?
I don't know how to implement what you want to do, except perhaps
implementing your own referential control in procedural sql functions fired
by triggers.
Anyhow, it is better design pattern to use sequential number without any
business meaning as primary key.
Luc Jouneau
----- Original Message -----
From: "sathish" <sathish@ceedees.com>
To: <pgsql-jdbc@postgresql.org>
Sent: Friday, June 11, 2004 11:44 AM
Subject: [ADMIN] doubt
> dear groups,
> i have a doubt in sql,
> i have a table staff_skills in which i have set a table level
> constraint to create a primary key of two fields .
> so 'name' and 'skill' combinedly forms a primary key.
> now the issue is in another table i have only 'name' field and i want
> to create a foreign key constraint which refers the staff_skills table's
> 'name' field only.
> staff_skills (table) - name,skill,ability (columns) --- primary
> key(name,skill)
> staff_xxxx (table) - name,x,y,z (columns) --- foreign
> key(name) references staff_skills(name).
> how to do the above?
> your immediate reply will be helpful
> yours sincerely
> SathishKumar.S
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
