在 PostgreSQL 8 中,是否可以添加ON DELETE CASCADES到下表中的两个外键而不删除后者?
ON DELETE CASCADES
# \d scores Table "public.scores" Column | Type | Modifiers ---------+-----------------------+----------- id | character varying(32) | gid | integer | money | integer | not null quit | boolean | last_ip | inet | Foreign-key constraints: "scores_gid_fkey" FOREIGN KEY (gid) REFERENCES games(gid) "scores_id_fkey" FOREIGN KEY (id) REFERENCES users(id)
两个引用的表格都在下面 - 这里:
# \d games Table "public.games" Column | Type | Modifiers ----------+-----------------------------+---------------------------------------------------------- gid | integer | not null default nextval('games_gid_seq'::regclass) rounds | integer | not null finished | timestamp without time zone | default now() Indexes: "games_pkey" PRIMARY KEY, btree (gid) Referenced by: TABLE "scores" CONSTRAINT "scores_gid_fkey" FOREIGN KEY (gid) REFERENCES games(gid)
和这里:
# \d users Table "public.users" Column | Type | Modifiers ------------+-----------------------------+--------------- id | character varying(32) | not null first_name | character varying(64) | last_name | character varying(64) | female | boolean | avatar | character varying(128) | city | character varying(64) | login | timestamp without time zone | default now() last_ip | inet | logout | timestamp without time zone | vip | timestamp without time zone | mail | character varying(254) | Indexes: "users_pkey" PRIMARY KEY, btree (id) Referenced by: TABLE "cards" CONSTRAINT "cards_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "catch" CONSTRAINT "catch_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "chat" CONSTRAINT "chat_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "game" CONSTRAINT "game_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "hand" CONSTRAINT "hand_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "luck" CONSTRAINT "luck_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "match" CONSTRAINT "match_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "misere" CONSTRAINT "misere_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "money" CONSTRAINT "money_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "pass" CONSTRAINT "pass_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "payment" CONSTRAINT "payment_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "rep" CONSTRAINT "rep_author_fkey" FOREIGN KEY (author) REFERENCES users(id) TABLE "rep" CONSTRAINT "rep_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "scores" CONSTRAINT "scores_id_fkey" FOREIGN KEY (id) REFERENCES users(id) TABLE "status" CONSTRAINT "status_id_fkey" FOREIGN KEY (id) REFERENCES users(id)
而且我想知道在前一张表中添加 2 个索引是否有意义?
更新: 谢谢,而且我在邮件列表中得到了建议,我可以在 1 条语句中管理它,因此无需明确启动交易:
ALTER TABLE public.scores DROP CONSTRAINT scores_gid_fkey, ADD CONSTRAINT scores_gid_fkey FOREIGN KEY (gid) REFERENCES games(gid) ON DELETE CASCADE;
我很确定您不能简单地添加on delete cascade到现有的外键约束。您必须先删除约束,然后添加正确的版本。在标准 SQL 中,我相信最简单的方法是
on delete cascade
对要更改的每个外键重复此操作。
但是 PostgreSQL 有一个非标准扩展,允许您在单个 SQL 语句中使用多个约束子句。例如
alter table public.scores drop constraint scores_gid_fkey, add constraint scores_gid_fkey foreign key (gid) references games(gid) on delete cascade;
如果您不知道要删除的外键约束的名称,您可以在 pgAdminIII 中查找(只需单击表名并查看 DDL,或者展开层次结构直到看到“约束”),或者您可以查询信息架构。
select * from information_schema.key_column_usage where position_in_unique_constraint is not null