From: Scott Marlowe <scott.marlowe@gmail.com>
To: Leif Biberg Kristensen <leif@solumslekt.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: DDL problems: Referential issue?
Date: Wed, 4 Nov 2009 11:37:41 -0700
Message-ID: <dcc563d10911041037p5fda84dv1c003c97c112cfc7@mail.gmail.com> (raw)
In-Reply-To: <200911041936.15292.leif@solumslekt.org>
References: <200911041903.36563.leif@solumslekt.org>
<dcc563d10911041024s67a3c313w1ed90c415840c2f7@mail.gmail.com>
<200911041936.15292.leif@solumslekt.org>
On Wed, Nov 4, 2009 at 11:36 AM, Leif Biberg Kristensen
<leif@solumslekt.org> wrote:
> On Wednesday 4. November 2009 19.24.29 Scott Marlowe wrote:
>> You're referencing a single column, which does not have a unique key
>> on it. Being part of a two column unique PK index doesn't count, as
>> you could have an entry where one column or the other repeats on its
>> own while the other column changes. You might want the syntax:
>>
>> FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn
>> [, ... ] )
>>
>> where you FK a pair of columns to a pair of other columns.
>
> Thank you very much!
>
> pgslekt=> CREATE TABLE participant_notes (
> pgslekt(> person_fk INTEGER,
> pgslekt(> event_fk INTEGER,
> pgslekt(> part_note TEXT,
> pgslekt(> FOREIGN KEY (person_fk, event_fk) REFERENCES participants
> (person_fk, event_fk)
> pgslekt(> );
> CREATE TABLE
>
> I'd missed that particular syntax.
>
> This table is now without a primary key, but is that a problem? I don't expect
> it to grow beyond maybe a few thousand rows.
Hard to say, but if you really need a PK, you can always create one later.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: scott.marlowe@gmail.com, leif@solumslekt.org
Subject: Re: DDL problems: Referential issue?
In-Reply-To: <dcc563d10911041037p5fda84dv1c003c97c112cfc7@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox