Makes sense. I think my question was more asking about the details of how
the pool (sql.DB) worked. So this clears it up. The driver would provide
the pool this connector to use vs the DNS string and that Connector could
re-auth etc... This definitely allows for what I am looking for to be
solv
I don't quite understand you question. It just allows drivers an alternate
way for the pool (sql.DB) to open a connection. Nothing ever is "returned".
On Thu, Nov 9, 2017 at 1:19 PM wrote:
> What would happen if idle/closed connections that are in the SQL
> interface's connection pool? They go b
What would happen if idle/closed connections that are in the SQL
interface's connection pool? They go back to the driver provided Connector
interface to re-authenticate/create a connection?
Thanks,
Anthony
On Thursday, November 9, 2017 at 10:49:00 AM UTC-8, Daniel Theophanes wrote:
>
> It allow
It allows drivers a way to provide a connection to the pool on demand,
without needing to go through a static connection string.
On Thu, Nov 9, 2017 at 9:09 AM wrote:
> So this would allow for the driver to support a different method of
> opening the connection that the sql interface would use w
So this would allow for the driver to support a different method of opening
the connection that the sql interface would use when it needed to open a
new connection correct?
Anthony
On Tuesday, November 7, 2017 at 9:44:05 AM UTC-8, Daniel Theophanes wrote:
>
> Go1.10 will ship with a driver conn
Go1.10 will ship with a driver
connector https://tip.golang.org/pkg/database/sql/driver/#Connector . It
would be possible for a driver to provide a callback function that returned
the most recent authentication parameters by using that.
Thanks, -Daniel
On Tuesday, November 7, 2017 at 5:34:20
