Add zero or more cleanup callbacks to be run when the savepoint is rolled back. Non-function values are ignored.
Link a child savepoint to this savepoint, such that the child will remove itself from the parent.
Similar to subtask(), except that you supply the child savepoint instead of it being created automatically.
The savepoint to link.
Optionalstop: (res: JobResult<unknown>) => unknownThe function the parent should call to roll back the subtask;
defaults to the subtask's rollback() method if not given.
The subtask savepoint.
Call all the added cleanup callbacks; if any throw exceptions, they're converted to unhandled promise rejections (so that all cleanups can be called even if one throws an error).
Invoke a function with this savepoint as the active one, so that savepoint.add()
will add things to it, savepoint.subtask() will fork it, and so on.
The result of calling fn(...args)
Create a single-use subordinate savepoint that rolls back if its parent does. (For long-lived parent savepoints that sequentially spin off lots of subordinate savepoints.)
This is similar to calling subtask = new savepoint(); parent.add(subtask.rollback);, but with an important difference: when
the subtask savepoint rolls back, it will remove its rollback from the
parent savepoint. This prevents a lot of useless callbacks accumulating
in the parent savepoint.
(Note that the link is a one-time thing: if you reuse the task savepoint
after it's been rolled back, you'll need to use parent.link(child, stop?) to re-attach it to the parent (or attach it to a different one)
Optionalstop: (res: JobResult<unknown>) => unknownThe function the parent should call to roll back the subtask;
defaults to the new task's rollback() method if not given.
A new linked savepoint
Deprecated
Use job APIs from uneventful instead