Short Term DSN for database/sql

[agru...@gmail.com]

It appears the Generic Interface for SQL (database/sql) does not support the ability to use short lived DSN's for cases like AWS's IAM Authentication to RDS instances. It appears that when doing its connection pooling activities it always uses whatever DSN was passed initially on Open.

1) Is this correct.

2) Assuming one is correct would the Golang project every consider adding this feature?

3) If the answer is yes. How would one go about either helping to get it on the road map or better yet contributing this feature back to the community? What is this process?

Thanks,

Anthony Gruetzmacher

[Konstantin Khomoutov]

Does setting the maximum number of the idle (that is, pooled) database
connections [1] to a value equal or less than zero helps with this?

1. https://golang.org/pkg/database/sql/#DB.SetMaxIdleConns

[agru...@gmail.com]

This does not help because if there is no connection in the connection pool the interface will open a new connection with previously supplied DSN from the sql.Open call.

Anthony

[Daniel Theophanes]

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

[agru...@gmail.com]

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

[Daniel Theophanes]

It allows drivers a way to provide a connection to the pool on demand, without needing to go through a static connection string.

--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/fl0GiIEmbLM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[agru...@gmail.com]

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

[Daniel Theophanes]

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".

[agru...@gmail.com]

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 solved. The next step would be to get an IAM Connector added into the driver. Anyway thank you for the response very helpful.

Anthony