[英]How does one write a DELETE CASCADE for postgres?
I'm manually constructing a DELETE CASCADE statement for postgres. 我正在为postgres手动构建DELETE CASCADE语句。
I have a 'transaction' and a 'slice' table, related as shown below: 我有一个'交易'和'切片'表,相关如下:
Table "public.slice"
Column | Type | Modifiers
----------+------+-----------
id | text | not null
name | text |
Referenced by:
TABLE "transaction" CONSTRAINT "transaction_slice_id_fkey" FOREIGN KEY (slice_id) REFERENCES slice(id)
Table "public.transaction"
Column | Type | Modifiers
----------+------+-----------
id | text | not null
slice_id | text |
Referenced by:
TABLE "classification_item" CONSTRAINT "classification_item_transaction_id_fkey" FOREIGN KEY (transaction_id) REFERENCES transaction(id)
Table "public.classification_item"
Column | Type | Modifiers
----------------+------+-----------
id | text | not null
transaction_id | text |
Foreign-key constraints:
"classification_item_transaction_id_fkey" FOREIGN KEY (transaction_id) REFERENCES transaction(id)
Say I want to delete all transactions and classification_items referenced by the slice whose name is 'my_slice'. 假设我想要删除名称为“my_slice”的切片引用的所有事务和classification_items。 What do I need to write? 我需要写什么?
=# delete from classification_item where transaction_id= #...?
=# delete from transaction where slice_id= #...?
=# delete from slice where name='my_slice';
Postgres foreign keys support the CASCADE deletes: Postgres外键支持CASCADE删除:
slice_id integer REFERENCES slice(id) ON DELETE CASCADE
etc 等等
In case you can't do what others have suggested: 万一你不能做别人的建议:
begin;
delete from classification_item where transaction_id in (select id from "transaction" where slice_id = (select id from slice where name = 'my_slice'));
delete from "transaction" where slice_id in (select id from slice where name='my_slice');
delete from slice where name='my_slice';
commit;
It's soemthing that is defined in the table rather than the DELETE Query. 它是在表中定义的soemthing而不是DELETE Query。 Example (look at order_id): 示例(查看order_id):
CREATE TABLE order_items (
product_no integer REFERENCES products ON DELETE RESTRICT,
order_id integer REFERENCES orders ON DELETE CASCADE,
quantity integer,
PRIMARY KEY (product_no, order_id)
);
You should use CASCADE deletes, and it should be possible to do so even if you inherited a database schema. 您应该使用CASCADE删除,即使您继承了数据库模式,也应该可以这样做。 You would just modify the constraints to add the CASCADE deletes to the schemas: 您只需修改约束以将CASCADE删除添加到模式:
Drop and re-create the constraints to add CASCADE deletes: 删除并重新创建约束以添加CASCADE删除:
ALTER TABLE ONLY "transaction" DROP CONSTRAINT transaction_slice_id_fkey; ALTER TABLE ONLY "transaction" ADD CONSTRAINT transaction_slice_id_fkey FOREIGN KEY (slice_id) REFERENCES slice(id) ON DELETE CASCADE; ALTER TABLE ONLY "classification_item" DROP CONSTRAINT classification_item_transaction_id_fkey; ALTER TABLE ONLY "classification_item" ADD CONSTRAINT classification_item_transaction_id_fkey FOREIGN KEY (transaction_id) REFERENCES transaction(id) ON DELETE CASCADE;
Now the following query will delete not just the my_slice
record from table slice
, but also all records from tables transaction
and classification_item
referencing it: 现在,以下查询不仅会从表slice
删除my_slice
记录,还会从表transaction
和classification_item
引用它的所有记录:
DELETE FROM slice WHERE name='my_slice';
That procedure will work even if the original schema is created by an object-relational mapper like SQLAlchemy. 即使原始模式由像SQLAlchemy这样的对象关系映射器创建,该过程也会起作用。 However in such a case, take care to re-apply that "patch" whenever the schema changes or is re-created. 但是,在这种情况下,每当架构更改或重新创建时,请务必重新应用该“补丁”。 Only if that can't be implemented automatically, it might not be a good idea after all … 只有当它不能自动实现时,它毕竟不是一个好主意......
It can be delegated to DBMS by set a constraint property 'On delete' = CASCADE. 可以通过设置约束属性“On delete”= CASCADE将其委派给DBMS。 Please see an example . 请看一个例子 。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.