update: *DB and Tx implement tha same interface "QueryExecuter" #933
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@max107
Hello! I just wanted to make one suggestion, and I'm a PR.
*DB and Tx to implement a common interface "QueryExecuter". Otherwise, if we want to handle transactions in the usecase layer in clean architecture, etc., the usecase must directly hold *bun.
*DB and bun.Tx to implement a common interface, it would be easier to use transaction processing in the usecase layer by using context.
For a concrete example, look at the following sample code(For the sake of simplification, usecase and repository are not interfaces but structs.)
repository layer
usecase layer
If you have any questions about something you are not sure about, please ask!