-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Add Transaction abstraction to detach from sql DB #104
Comments
Hello, if I add the solution code, could you review and commit the code to the repository? |
hey @maranqz! appreciate the reach out and ideation here! thanks for the examples - admittedly i'm still a little fuzzy on the use cases being presented here, given the
It's my understanding that |
Hello, you are right about SQL. I could add an use case with NoSQL DBs, which support the transaction, but it is not so frequent. |
Hello,
sqlUnit is strongly connected with database/sql because of *sql.Tx.
However, sql.Tx could be placed in an interface with Begin, Commit and Rollback functions.
That gives the ability to change databases without changes the unit implementation.
What do you think about the idea?
interface{} version
generic version
The text was updated successfully, but these errors were encountered: