how about let mutation operation has transaction ability automatically?

[bonafideyan]

What happened?

nothing

What did you expect?

I can omit lots lines for transaction, such as db.rollback, db.commit

[giautm]

Hi @bonafideyan, because it depends on the Database driver / ORM that you used in your project. So, I think GQLGen can't do it automatically. However, you can apply the flowing pattern:

1. Open Transaction use graphql.HandlerExtension, and attach it to the Go's context object.
2. In your mutations, you can get the Tx object from the context and do the updates. If something go wrong, just return the error and the extension in step 1) will call rollback automatic

We (Ent/EntGQL) applied this pattern in our implementation. So, you can check out the example here for detail and here. This also can apply to the regular SQL driver:

[bonafideyan]

Thank you. That is a perfect solution.
I have read it, but don't know why:
at line 94 of file transaction.go, panic(r) after rollback, does it terminate the process? I usually write it as rollback and log it, can I remove the panic line?

[giautm]

Yes, you can remove the panic and log the error.