PostgreSQL外键不存在,继承问题?

Luk*_*kas 9 postgresql inheritance foreign-keys

我在我的数据库中苦苦寻找外键,可能它与继承有关?
所以这是基本设置:

-- table address
CREATE TABLE address
(
  pk_address serial NOT NULL,
  fk_gadmid_0 integer NOT NULL, -- this table already exists, no problem here
  street character varying(100),
  zip character varying(10),
  city character varying(50),
  public boolean,
  CONSTRAINT address_primarykey PRIMARY KEY (pk_address),
  CONSTRAINT gadmid_0_primarykey FOREIGN KEY (fk_gadmid_0)
      REFERENCES adm0 (gadmid_0) MATCH SIMPLE
      ON UPDATE CASCADE ON DELETE NO ACTION
)
WITH (
  OIDS=FALSE
);
ALTER TABLE address OWNER TO postgres;  

-- table stakeholder (parent)
CREATE TABLE stakeholder
(
    pk_stakeholder integer DEFAULT nextval('common_stakeholder_seq') NOT NULL,
    fk_stakeholder_type integer NOT NULL, -- this table also exists, no problem here
    name character varying(255) NOT NULL,
    CONSTRAINT stakeholder_primarykey PRIMARY KEY (pk_stakeholder),
    CONSTRAINT stakeholder_fk_stakeholder_type FOREIGN KEY (fk_stakeholder_type)
        REFERENCES stakeholder_type (pk_stakeholder_type) MATCH SIMPLE
        ON UPDATE CASCADE ON DELETE NO ACTION
)
WITH (
    OIDS=FALSE
);
ALTER TABLE stakeholder OWNER TO postgres;  

-- table individual (child of stakeholder)
CREATE TABLE individual
(
    firstname character varying(50),
    fk_title integer, -- this table also exists, no problem here
    email1 character varying (100),
    email2 character varying (100),
    phone1 character varying (50),
    phone2 character varying (50),
    CONSTRAINT individual_primarykey PRIMARY KEY (pk_stakeholder),
    CONSTRAINT title_foreignkey FOREIGN KEY (fk_title)
        REFERENCES title (pk_title) MATCH SIMPLE
        ON UPDATE CASCADE ON DELETE CASCADE
) INHERITS (stakeholder)
WITH (
    OIDS=FALSE
);
ALTER TABLE individual OWNER TO postgres;  

-- link between stakeholder and address
CREATE TABLE l_stakeholder_address
(
    pk_l_stakeholder_address serial NOT NULL,
    fk_stakeholder integer NOT NULL REFERENCES stakeholder,
    fk_address integer NOT NULL REFERENCES address,
    CONSTRAINT l_stakeholder_address_primarykey PRIMARY KEY (pk_l_stakeholder_address),
    CONSTRAINT l_stakeholder_address_fk_stakeholder FOREIGN KEY (fk_stakeholder)
        REFERENCES stakeholder (pk_stakeholder) MATCH SIMPLE
        ON UPDATE CASCADE ON DELETE NO ACTION,
    CONSTRAINT l_stakeholder_address_fk_address FOREIGN KEY (fk_address)
        REFERENCES address (pk_address) MATCH SIMPLE
        ON UPDATE CASCADE ON DELETE NO ACTION
)
WITH (
    OIDS=FALSE
);
ALTER TABLE l_stakeholder_address OWNER TO postgres;
Run Code Online (Sandbox Code Playgroud)

到目前为止,没问题.然后我尝试添加一些值:

INSERT INTO individual (pk_stakeholder, fk_stakeholder_type, name, firstname, fk_title, email1, email2, phone1, phone2) 
  VALUES (1, 8, 'Lastname', 'Firstname', 1, 'me@you.com', '', '', '');
INSERT INTO address (pk_address, fk_gadmid_0, street, zip, city, public)  
  VALUES (1, 126, 'Address', '', 'City', FALSE);
INSERT INTO l_stakeholder_address (pk_l_stakeholder_address, fk_stakeholder, fk_address)  
  VALUES (DEFAULT, 1, 1);
Run Code Online (Sandbox Code Playgroud)

最后我得到一个错误(SQL状态23503),表示密钥(fk_stakeholder)=(1)不存在于表"利益相关者"中.
前两个插入很好,我可以在数据库中看到它们:

stakeholder:
pk_stakeholder | ...
----------------------
1              | ...

address:
pk_address | ...
--------------------
1          | ...
Run Code Online (Sandbox Code Playgroud)

我究竟做错了什么?我必须承认我对PostgreSQL很新(使用8.4),但我甚至不确定这是否是PG的问题,也许我只是缺乏一些基本的数据库设计理解......
无论哪种方式,到现在为止我尝试了几乎所有我能想到的东西,我也试图让FK像PostgreSQL一样可以推迟:交易和外键问题,但不知怎的,它也不起作用.

Pet*_*aut 6

你的分析是完全正确的:这是因为继承.检查外键时,不考虑子表.

通常,继承和外键在PostgreSQL中不能很好地混合.一个主要问题是您不能在表之间具有唯一约束.

参考

  • 运行`SELECT*FROM ONLY stakeholder`.这就是FK检查的作用.那里没有排. (3认同)

Tom*_*zky 6

您可以使用individual_pks (individual_pk integer primary key)包含来自父级和子级的所有主键的附加表来解决它,这将使用触发器进行维护(非常简单 - 插入individual_pks插入,删除时删除,更新时更新,如果更改individual_pk).

然后将外键指向此附加表而不是子表.只会在添加/删除行时出现一些小的性能损失.

或者忘记继承并以旧方式执行 - 只需一个带有一些可为空列的表.