Re: no dup rows

Поиск
Список
Период
Сортировка
От Reece Hart
Тема Re: no dup rows
Дата
Msg-id 1091473791.16547.89.camel@tallac
обсуждение исходный текст
Ответ на no dup rows  (Jodi Kanter <jkanter@virginia.edu>)
Список pgsql-admin
On Mon, 2004-08-02 at 11:32, Jodi Kanter wrote:
I have a linking table that has only two fields in it and both are foreign keys to other tables. I'd like to ensure that there are never any duplicate rows in this table. I was planning on creating a multi-column unique index to satisfy this requirement. Is there a more appropriate way to accomplish this or am I on the right track?>

Yep, that is the correct way to impose this constraint.

I give constraints meaningful names prefixed by the table name (e.g., tablename_seq_already_in_set) so that the cause of an error is more readily identifiable. This is particularly useful for insertions into complex tables with multiple constraints.

-Reece
-- 
Reece Hart, Ph.D.                  rkh@gene.com, http://www.gene.com/
Genentech, Inc.                    650-225-6133 (voice), -5389 (fax)
Bioinformatics and Protein Engineering
1 DNA Way, MS-93                   http://www.in-machina.com/~reece/
S. San Francisco, CA  94080-4990   reece@in-machina.com, GPG: 0x25EC91A0

В списке pgsql-admin по дате отправления:

Предыдущее
От: Bill Harper
Дата:
Сообщение: Re: no dup rows
Следующее
От: LISTMAN
Дата:
Сообщение: Re: [HACKERS] Where does the xlateSqlType symbol point