Amin Alaee

@trvrm This is probably fixed by #328 . Please re-open if it still exists.

@trvrm Thanks, I'll take a look into it.

Hi, thanks for the PR. Can you maybe include the tests for it?

I think this is the same as #403.

I'm not really sure how to fix it. The only way I could fix it was by reverting parallel transactions [here](https://github.com/encode/databases/issues/403#issuecomment-939446626). Still waiting for a reply there.

@jakehu I guess that test uses nested transactions, specifically `database.transaction(force_rollback=True` (the outer one) to rollback when test finishes.

I think that's not related, this should work too: ```python transaction = await conn.transaction() try: query = user.insert().values(**row["data"]) await conn.execute(query=query) query_sms = ( user_sms.update() .where(user_sms.c.ccode == "code") .values(status=1) ) await...

@jakehu Cqn you test and post traceback of when you run [this](https://github.com/encode/databases/issues/425#issuecomment-994497571) sample.

Hey, can you share the full traceback? Or the query logged by `databases`? My guess is that since we're doing `compile` query with SQLAlchemy and the `RETURNING` clause is not...

Hi, I think for the first one that sounds reasonable, we could turn the `tests` into a package. But for the second point, I'm not sure what needs to be...