DBIOAction
Related Doc:
package dbio
A shortcut for andThen.
Run another action after this action, whether it succeeds or fails, and then return the result of the first action.
Run another action after this action, whether it succeeds or fails, and then return the result of the first action. If the first action fails, its failure is propagated, whether the second action fails or succeeds. If the first action succeeds, a failure of the second action is propagated.
Run another action after this action, if it completed successfully, and return the result of the second action.
Run another action after this action, if it completed successfully, and return the result of the second action. If either of the two actions fails, the resulting action also fails.
Convert a successful result v of this action into a successful result Success(v) and a
failure t into a successful result Failure(t).
Convert a successful result v of this action into a successful result Success(v) and a
failure t into a successful result Failure(t). This is the most generic combinator that
can be used for error recovery. If possible, use andFinally or cleanUp instead,
because those combinators, unlike asTry, support streaming.
Run another action after this action, whether it succeeds or fails, in order to clean up or transform an error produced by this action.
Run another action after this action, whether it succeeds or fails, in order to clean up or
transform an error produced by this action. The clean-up action is computed from the failure
of this action, wrapped in Some, or None if this action succeeded.
If this action returns successfully, the resulting action also returns
successfully unless the clean-up action fails. If this action fails and
keepFailure is set to true (the default), the resulting action fails
with the same error, no matter whether the clean-up action succeeds or
fails. If keepFailure is set to false, an error from the clean-up
action will override the error from this action.
Return an action which contains the Throwable with which this action failed as its result.
Return an action which contains the Throwable with which this action failed as its result. If this action succeeded, the resulting action fails with a NoSuchElementException.
Filter the result of this action with the given predicate.
Filter the result of this action with the given predicate. If the predicate matches, the original result is returned, otherwise the resulting action fails with a NoSuchElementException.
Use the result produced by the successful execution of this action to compute and then run the next action in sequence.
Use the result produced by the successful execution of this action to compute and then run the next action in sequence. The resulting action fails if either this action, the computation, or the computed action fails.
Whether or not this action should be included in log output by default.
Transform the result of a successful execution of this action.
Transform the result of a successful execution of this action. If this action fails, the resulting action also fails.
Get a wrapping action which has a name that will be included in log output.
Get the equivalent non-fused action if this action has been fused, otherwise this action is returned.
Use a pinned database session when running this action.
Use a pinned database session when running this action. If it is composed of multiple database actions, they will all use the same session, even when sequenced with non-database actions. For non-composite or non-database actions, this has no effect.
Run another action after this action, if it completed successfully, and return the result of both actions.
Run another action after this action, if it completed successfully, and return the result of both actions. If either of the two actions fails, the resulting action also fails.
A Database I/O Action that can be executed on a database. The DBIOAction type allows a separation of execution logic and resource usage management logic from composition logic. DBIOActions can be composed with methods such as
andThen,andFinallyandflatMap. Individual parts of a composite DBIOAction are always executed serially on a single database, but possibly in different database sessions, unless the session is pinned either explicitly (usingwithPinnedSession) or implicitly (e.g. through a transaction).The actual implementation base type for all Actions is
DBIOAction.StreamingDBIOandDBIOare type aliases which discard the effect type (and the streaming result type in the latter case) to make DBIOAction types easier to write when these features are not needed. All primitive DBIOActions and all DBIOActions produced by the standard combinators in Slick have correct Effect types and are streaming (if possible).The result type when executing the DBIOAction and fully materializing the result.
An encoding of the result type for streaming results. If this action is capable of streaming, it is
Streaming[T]for an element typeT. For non-streaming DBIOActions it isNoStream.The DBIOAction's effect type, e.g.
Effect.Read with Effect.Write. When composing actions, the correct combined effect type will be inferred. Effects can be used in user code, e.g. to automatically direct all read-only Actions to a slave database and write Actions to the master copy.