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'. What do I need to write?
假设我想删除名称为“my_slice”的切片引用的所有事务和classification_items。我需要写什么?
=# delete from classification_item where transaction_id= #...?
=# delete from transaction where slice_id= #...?
=# delete from slice where name='my_slice';
5 个解决方案
#1
12
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;
#2
46
Postgres foreign keys support the CASCADE deletes:
Postgres外键支持CASCADE删除:
slice_id integer REFERENCES slice(id) ON DELETE CASCADE
etc
等等
#3
8
It's soemthing that is defined in the table rather than the DELETE Query. Example (look at order_id):
它是在表中定义的soemthing而不是DELETE Query。示例(查看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)
);
#4
6
You should use CASCADE deletes, and it should be possible to do so even if you inherited a database schema. You would just modify the constraints to add the CASCADE deletes to the schemas:
您应该使用CASCADE删除,即使您继承了数据库模式,也应该可以这样做。您只需修改约束以将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 tableslice
, but also all records from tablestransaction
andclassification_item
referencing it:现在,以下查询不仅会删除表切片中的my_slice记录,还会删除tablestransaction和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. 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 …
即使原始模式由像SQLAlchemy这样的对象关系映射器创建,该过程也会起作用。但是,在这种情况下,每当架构更改或重新创建时,请务必重新应用该“补丁”。只有当它不能自动实现时,它毕竟不是一个好主意......
#5
0
It can be delegated to DBMS by set a constraint property 'On delete' = CASCADE. Please see an example.
可以通过设置约束属性“On delete”= CASCADE将其委派给DBMS。请看一个例子。
#1
12
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;
#2
46
Postgres foreign keys support the CASCADE deletes:
Postgres外键支持CASCADE删除:
slice_id integer REFERENCES slice(id) ON DELETE CASCADE
etc
等等
#3
8
It's soemthing that is defined in the table rather than the DELETE Query. Example (look at order_id):
它是在表中定义的soemthing而不是DELETE Query。示例(查看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)
);
#4
6
You should use CASCADE deletes, and it should be possible to do so even if you inherited a database schema. You would just modify the constraints to add the CASCADE deletes to the schemas:
您应该使用CASCADE删除,即使您继承了数据库模式,也应该可以这样做。您只需修改约束以将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 tableslice
, but also all records from tablestransaction
andclassification_item
referencing it:现在,以下查询不仅会删除表切片中的my_slice记录,还会删除tablestransaction和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. 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 …
即使原始模式由像SQLAlchemy这样的对象关系映射器创建,该过程也会起作用。但是,在这种情况下,每当架构更改或重新创建时,请务必重新应用该“补丁”。只有当它不能自动实现时,它毕竟不是一个好主意......
#5
0
It can be delegated to DBMS by set a constraint property 'On delete' = CASCADE. Please see an example.
可以通过设置约束属性“On delete”= CASCADE将其委派给DBMS。请看一个例子。