me".
>
> I would love a working proposal that would take the place of ocsql, or at
> least provide it hooks to work without wrapping it.
>
> On Friday, September 21, 2018 at 6:32:40 AM UTC-7, Bas Van Beek wrote:
>>
>>
>> The preferred method of working with
wrap the driver? Why not just the db?
>
> 2018. szeptember 21., péntek 15:32:40 UTC+2 időpontban Bas Van Beek a
> következőt írta:
>>
>>
>> The preferred method of working with database/sql is to use registered
>> driver names to identify which driver to use for con
ith ocsql also does not export its
driver.Driver implementation it will be not possible to use ocsql.
Would like to hear from the Go team and community if adding a DriverByName
type function is acceptable given the use case presented above. It would
surely make ocsql less brittle and bette
That should work and probably is working. I expect h.ServeHTTP not
returning as quickly as you expect it to.
What you could try to do to test if there is an issue with decreasing the
atomic value is to split up concur into two counters, one for entry and one
for exit. The difference between the
