pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Allan Engelhardt <allane@cybaea.com>
To: pgsql-sql@postgresql.org
Subject: Creating foreign key constraint to child table?
Date: Sun, 05 Aug 2001 13:49:22 +0100
Message-ID: <3B6D40D2.BDF7B876@cybaea.com> (raw)

I would like to create a FOREIGN KEY constraint to an inherited column, like:

    test=# CREATE TABLE foo(id INTEGER PRIMARY KEY);
    test=# CREATE TABLE bar() INHERITS (foo);
    test=# CREATE TABLE baz (bar INTEGER, CONSTRAINT fk_bar FOREIGN KEY (bar) REFERENCES bar(id));
    ERROR:  UNIQUE constraint matching given keys for referenced table "bar" not found

This obvioulsy doesn't work.  I *can* create a FOREIGN KEY contraint to the parent table:

    test=# create table baz(bar integer, constraint fk_bar foreign key (bar) references foo(id));
    NOTICE:  CREATE TABLE will create implicit trigger(s) for FOREIGN KEY check(s)
    CREATE

but this is not exactly what I want: I need to ensure that baz.bar is a bar and not just any foo.

Do I need to write my own INSERT/UPDATE triggers on baz to check the tableoid, or is there a nice way to do this?

Any examples on how to do this?  In particular, do I need to do a SELECT on pg_class for every INSERT / UPDATE in baz, just to get the tableoid for bar ?  There *is* an index on pg_class.relname but still...


    --- Allan.




view thread (5+ messages)  latest in thread

Message-ID: <3B6D40D2.BDF7B876@cybaea.com>
Permalink:  ../3B6D40D2.BDF7B876@cybaea.com/
Also on:    postgresql.org/message-id/3B6D40D2.BDF7B876@cybaea.com

 · 

reply

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: allane@cybaea.com
  Subject: Re: Creating foreign key constraint to child table?
  In-Reply-To: <3B6D40D2.BDF7B876@cybaea.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