-
Daniel Theophanes authored
The logic for pulling a database connection from the DB pool should proceed as follows: attempt to pull either a cached connection or new connection N times in a loop. If each connection results in a bad connection, then create a new connection (no cache). Previously pulling a Conn from the pool, the last step also looked at the cache, rather then always creating a new connection. Fixes #29684 Change-Id: I8f436fd9b96eb35502a620ebe8da4ab89fb06a2e Reviewed-on: https://go-review.googlesource.com/c/157637Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
70931c08
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
driver | ||
convert.go | ||
convert_test.go | ||
ctxutil.go | ||
doc.txt | ||
example_cli_test.go | ||
example_service_test.go | ||
example_test.go | ||
fakedb_test.go | ||
sql.go | ||
sql_test.go |