postgresql – 如何添加“关于删除级联”约束?

前端之家收集整理的这篇文章主要介绍了postgresql – 如何添加“关于删除级联”约束?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
在Postgresql 8中,可以在下表中的两个外键上添加删除级联”,而不删除后者?
  1. # \d pref_scores
  2. Table "public.pref_scores"
  3. Column | Type | Modifiers
  4. ---------+-----------------------+-----------
  5. id | character varying(32) |
  6. gid | integer |
  7. money | integer | not null
  8. quit | boolean |
  9. last_ip | inet |
  10. Foreign-key constraints:
  11. "pref_scores_gid_fkey" FOREIGN KEY (gid) REFERENCES pref_games(gid)
  12. "pref_scores_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)

两个参考表如下:

  1. # \d pref_games
  2. Table "public.pref_games"
  3. Column | Type | Modifiers
  4. ----------+-----------------------------+----------------------------------------------------------
  5. gid | integer | not null default nextval('pref_games_gid_seq'::regclass)
  6. rounds | integer | not null
  7. finished | timestamp without time zone | default now()
  8. Indexes:
  9. "pref_games_pkey" PRIMARY KEY,btree (gid)
  10. Referenced by:
  11. TABLE "pref_scores" CONSTRAINT "pref_scores_gid_fkey" FOREIGN KEY (gid) REFERENCES pref_games(gid)
  12.  
  13.  
  14. # \d pref_users
  15. Table "public.pref_users"
  16. Column | Type | Modifiers
  17. ------------+-----------------------------+---------------
  18. id | character varying(32) | not null
  19. first_name | character varying(64) |
  20. last_name | character varying(64) |
  21. female | boolean |
  22. avatar | character varying(128) |
  23. city | character varying(64) |
  24. login | timestamp without time zone | default now()
  25. last_ip | inet |
  26. logout | timestamp without time zone |
  27. vip | timestamp without time zone |
  28. mail | character varying(254) |
  29. Indexes:
  30. "pref_users_pkey" PRIMARY KEY,btree (id)
  31. Referenced by:
  32. TABLE "pref_cards" CONSTRAINT "pref_cards_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  33. TABLE "pref_catch" CONSTRAINT "pref_catch_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  34. TABLE "pref_chat" CONSTRAINT "pref_chat_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  35. TABLE "pref_game" CONSTRAINT "pref_game_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  36. TABLE "pref_hand" CONSTRAINT "pref_hand_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  37. TABLE "pref_luck" CONSTRAINT "pref_luck_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  38. TABLE "pref_match" CONSTRAINT "pref_match_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  39. TABLE "pref_misere" CONSTRAINT "pref_misere_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  40. TABLE "pref_money" CONSTRAINT "pref_money_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  41. TABLE "pref_pass" CONSTRAINT "pref_pass_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  42. TABLE "pref_payment" CONSTRAINT "pref_payment_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  43. TABLE "pref_rep" CONSTRAINT "pref_rep_author_fkey" FOREIGN KEY (author) REFERENCES pref_users(id)
  44. TABLE "pref_rep" CONSTRAINT "pref_rep_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  45. TABLE "pref_scores" CONSTRAINT "pref_scores_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)
  46. TABLE "pref_status" CONSTRAINT "pref_status_id_fkey" FOREIGN KEY (id) REFERENCES pref_users(id)

并且我想知道是否有意义,添加2 index’es到前表?

更新:谢谢,我也有在邮件列表的建议,我可以管理它在1语句,因此不需要一个事务:

  1. ALTER TABLE public.pref_scores
  2. DROP CONSTRAINT pref_scores_gid_fkey,ADD CONSTRAINT pref_scores_gid_fkey
  3. FOREIGN KEY (gid)
  4. REFERENCES pref_games(gid)
  5. ON DELETE CASCADE;
我很确定你不能简单地添加删除级联到现有的外键约束。您必须先删除约束,然后添加正确的版本。在标准sql中,我相信最简单的方法是做到这一点

>开始一个事务,
>丢弃外键,
>添加外键与删除级联,最后
>提交事务

对要更改的每个外键重复此操作。

但是Postgresql有一个非标准的扩展,它允许在单个sql语句中使用多个约束子句。例如

  1. alter table public.pref_scores
  2. drop constraint pref_scores_gid_fkey,add constraint pref_scores_gid_fkey
  3. foreign key (gid)
  4. references pref_games(gid)
  5. on delete cascade;

如果你不知道你想要删除的外键约束的名称,你可以在pgAdminIII中查找(只需点击表名称并查看DDL,或者展开层次结构直到你看到“约束”),或者你可以query the information schema

  1. select *
  2. from information_schema.key_column_usage
  3. where position_in_unique_constraint is not null

猜你在找的Postgre SQL相关文章