User Tools

Site Tools


01_user_documentation:03_interacting_with_groimp:20_delete:01_node

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
01_user_documentation:03_interacting_with_groimp:20_delete:01_node [2025/09/05 17:20] – removed - external edit (Unknown date) 127.0.0.101_user_documentation:03_interacting_with_groimp:20_delete:01_node [2025/09/05 17:20] (current) – ↷ Page moved from 01_user_documentation:03_interacting_with_groimp:08_delete:01_node to 01_user_documentation:03_interacting_with_groimp:20_delete:01_node gaetan
Line 1: Line 1:
 +====== Node ======
 +
 +Remove all edges between the node (or nodes) and the project graph. After the edges are deleted, all nodes in the graph that are not connected to it anymore are marked as transient. Transient nodes cannot be queried, and will be properly deleted by the java garbage collector.
 +
 +===== =====
 +
 +Only the edges of the deleted node(s) are included in the  [[:01_user_documentation:06_graph:05_derivation:02_transaction|transaction]] responsible for the deletion. Thus, children nodes of the deleted nodes are not "notified" in the transaction that they are set transient. 
 +
 +It is possible to ensure that a Node dispose a specific field when set transient by having the field implements ''de.grogra.persistence.DisposableField''. The field needs to then, provide a implementation of the ''public void disposeField()'' method.