Lift a scala.concurrent.Future into a DBIOAction.

This overload is provided for interop with Play / Akka / Pekko code that produces Future values. The Future is wrapped in cats.effect.IO.fromFuture so that it is executed on the CE3 compute pool and its cancellation semantics are respected.

def callExternalService(): Future[String] = ???
val action: DBIO[String] = DBIO.from(callExternalService())

For lifting a CE3 effect use DBIO.from[F[_], R](fa: F[R]) directly.

Warning — do not call db.run inside the lifted Future. See the DBIO.from[F[_], R] overload for a full explanation of why nested db.run calls can cause a deadlock.

Lift any F[R] effect (e.g. cats.effect.IO[R]) into a DBIOAction.

The effect is executed on the CE3 compute pool, outside of any JDBC blocking context. Use this to interleave effectful computations (logging, UUID generation, etc.) within a DBIO action chain without needing a separate flatMap over F.

val action: DBIO[String] = for {
  id <- DBIO.from(IO(java.util.UUID.randomUUID().toString))
  _  <- users += User(id, "Alice")
} yield id

Warning — do not call db.run inside the lifted effect. db.run acquires a connection-pool permit for the full duration of the outer action. Calling db.run again from within DBIO.from attempts to acquire a second permit from the same bounded pool. If all permits are already held by outer actions, every inner db.run will block forever, deadlocking the application. Compose database work as a single DBIO chain instead:

// Wrong — nested db.run can deadlock:
DBIO.from(db.run(otherAction))

// Correct — compose as DBIO:
otherAction.flatMap(result => nextAction(result))

Alias for from.

Warning — do not call db.run inside the lifted effect. See DBIO.from[F[_], R] for a full explanation of why nested db.run calls can cause a deadlock.

A no-op DBIOAction. A cached value of DBIOAction.successful(()) to avoid allocations.