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 On Thursday, November 9, 2017 at 1:45:14 PM UTC-8, Daniel Theophanes wrote: > > 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 <agru...@gmail.com <javascript:>> wrote: > >> 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 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 <agru...@gmail.com> wrote: >>> >> 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 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 AM UTC-8, Anthony Gruetzmacher >>>>> wrote: >>>>>> >>>>>> 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 >>>>>> >>>>> -- >>>> 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. >>>> >>> -- >> 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 <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
