Please read the 0.7 changelog and look at the current examples. This is not a bug, just a breaking change how transactions are used

@goodjius .
I was struggling with the same issue but exact advice from the changelog did not help, also I did not find example of the transaction for sqlite.

Here is the relevant part of the changelog mentioned by @dragonnn

The Executor impls for Transaction and PoolConnection have been deleted because they cannot exist in the new crate architecture without rewriting the Executor trait entirely.
To fix this breakage, simply add a dereference where an impl Executor is expected, as they both dereference to the inner connection type which will still implement it:
&mut transaction -> &mut *transaction
&mut connection -> &mut *connection

What helped was using as_mut. (although I am using connection.transaction)

My example

        self.conn.transaction(|tx| Box::pin(async move {
            sqlx::query(
                r#"...
            "#,
            ).bind(...)
             .execute(tx.as_mut())
             .await?;


            Ok::<_, eyre::Error>(())
        })).await?;

In your example this would be:

        let mut tx = pool.begin().await?;
        let res = sqlx::query("DELETE FROM \"testcases\" WHERE id = $1")
            .bind(id)
            .execute(tx.as_mut()) // <-- here
            .await?
            .rows_affected();

        tx.commit().await?;

Hi, sorry for bumping this old issue. I stumbled across the same problem, I wanted to use a transaction in a personal project and I wasn't able to get it to work at first. The examples in this repo were able to help me and I got it working, but I think it would be nice to add a short example on how to use Transaction as an executor to the docs.

Is that a good idea? If yes, I would submit a PR 😄.

@Lachstec Yes please do it.

@fosskers Okay, I will get to it if I find some time today.

@fosskers I've submitted a PR where I added a Snippet inspired by the one in this issue, hope that it is fine like that :)