Re: DDL problems: Referential issue?

From: Leif Biberg Kristensen <leif(at)solumslekt(dot)org>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: DDL problems: Referential issue?
Date: 2009-11-04 18:53:11
Message-ID: 200911041953.11714.leif@solumslekt.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Wednesday 4. November 2009 19.37.41 Scott Marlowe wrote:
> On Wed, Nov 4, 2009 at 11:36 AM, Leif Biberg Kristensen
> <leif(at)solumslekt(dot)org> wrote:
>> 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.

This looks strange to me, but it works:

pgslekt=> CREATE TABLE participant_notes (
pgslekt(> person_fk INTEGER NOT NULL,
pgslekt(> event_fk INTEGER NOT NULL,
pgslekt(> part_note TEXT,
pgslekt(> PRIMARY KEY (person_fk, event_fk),
pgslekt(> FOREIGN KEY (person_fk, event_fk) REFERENCES participants
(person_fk, event_fk)
pgslekt(> );
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"participant_notes_pkey" for table "participant_notes"
CREATE TABLE

And is probably what I want.
--
Leif Biberg Kristensen
http://solumslekt.org

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Scott Marlowe 2009-11-04 20:03:26 Re: DDL problems: Referential issue?
Previous Message Scott Marlowe 2009-11-04 18:37:41 Re: DDL problems: Referential issue?