You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a package that wraps an sql.Driver and adds functionality.
To test it, I'm trying to use go-sqlmock.
I'm running into the issue that if I wrap the go-sqlmock Driver, all operations fail with the error: expected a connection to be available, but it is not
The comment #83 (comment) seems to be about the same issue.
I guess it's not intended to be used like that, but it would be awesome to support operations on the go-sqlmock Driver.
The text was updated successfully, but these errors were encountered:
@l3pp4rd depends on the effort :-). I ended up writing my own simple mock instead, that works okayish for my current usecase.
Do you maybe have an idea what the cause it how it could be fixed?
Hello,
I'm working on a package that wraps an sql.Driver and adds functionality.
To test it, I'm trying to use go-sqlmock.
I'm running into the issue that if I wrap the go-sqlmock Driver, all operations fail with the error:
expected a connection to be available, but it is not
I'm accessing the driver via:
This can be reproduced e.g. via sqlmw:
Without using other external packages and mimicking the wrapping behavior instead it can be reproduced like:
The comment #83 (comment) seems to be about the same issue.
I guess it's not intended to be used like that, but it would be awesome to support operations on the go-sqlmock Driver.
The text was updated successfully, but these errors were encountered: