Gediminas Morkevicius

well, this is something that I do not like. the reasons are: 1. it will force sqlmock to lose the strict ordered matching. 2. it adds more than needed to...

Hi, maybe you can try and investigate what change needs to be added and submit a PR.

Have you read the api docs of sqlmock before asking?

many people are using gorm, I'm sure you are doing something wrong. you do not even check the errors. opening a gorm db may give you an error

yes, sadly the reason is: 1. the rows were not closed or garbage collected for the q1P. 2. in go sql standard library the connection is held on Rows until...

Hi, **AnyArg** was added only for corner cases like **time.Time** or other arguments, which simply cannot be generated for assertion. If you start to build your tests with `Any*Types` your...

Haven't read it well the first time. It would have been better to add **AnyTime** instead of **AnyArg** in the beginning. **AnyTime** is considerable, but I doubt that it would...

Maybe, first of all a Wiki page could be created with some code samples for such arguments and then referenced in the documentation. And only later considered whether worth moving...

What is the point of a test if it is not strict? How can devs push commits without updates for tests? And why then you write tests in the first...

well, my intention for this library is to be used for unit tests. if you are testing a **unit** which is too large and may have unexpected behaviors in terms...