From: | Anton Gavazuk <antongavazuk(at)gmail(dot)com> |
---|---|
To: | JORGE MALDONADO <jorgemal1960(at)gmail(dot)com> |
Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Advice on key design |
Date: | 2013-07-23 22:02:43 |
Message-ID: | 3311319936507639588@unknownmsgid |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi Jorge,
In your case it would be lpp_id as PK, and
lpp_person_id,lpp_language_id as unique constraint
Thanks,
Anton
On Jul 23, 2013, at 23:45, JORGE MALDONADO <jorgemal1960(at)gmail(dot)com> wrote:
> I have 2 tables, a parent (tbl_persons) and a child (tbl_languages_per_person) as follows (a language table is also involved):
>
> ------------------
> tbl_persons
> ------------------
> * per_id
> * per_name
> * per_address
>
> --------------------------------------
> tbl_languages_per_person
> --------------------------------------
> * lpp_person_id
> * lpp_language_id
> * lpp_id
>
> As you can see, there is an obvious key in the child table which is "lpp_person_id + lpp_language_id", but I also need the field "lpp_id" as a unique key which is a field that contains a consecutive number of type serial.
>
> My question is: what should I configure as the primary key, "lpp_person_id + lpp_language_id" or "lpp_id"?
> Is the role of a primary key different from that of a unique index?
>
> With respect,
> Jorge Maldonado
>
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | JORGE MALDONADO | 2013-07-23 22:28:33 | Re: Advice on key design |
Previous Message | JORGE MALDONADO | 2013-07-23 21:44:20 | Advice on key design |