01_user_documentation:06_graph:05_derivation:02_transaction
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 01_user_documentation:06_graph:05_derivation:02_transaction [2025/01/30 11:38] – created gaetan | 01_user_documentation:06_graph:05_derivation:02_transaction [2025/11/03 05:34] (current) – gaetan | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Transaction ====== | ====== Transaction ====== | ||
| - | Not sure if this should be a section or a " | + | Not sure if this should be a section or a " |
| - | ====== ====== | + | Transactions act as buffers for operations on the project graph. Each transaction maintains a set of **queues**, where each queue holds a list of modifications to be applied to the graph. When any **RGG method** is executed, GroIMP automatically creates a transaction if one does not already exist. All subsequent graph modifications during that operation are pushed into the current transaction' |
| + | |||
| + | ====== | ||
| {{namespace>: | {{namespace>: | ||
01_user_documentation/06_graph/05_derivation/02_transaction.1738233527.txt.gz · Last modified: 2025/01/30 11:38 by gaetan
