Daniel, I agree that multiple queries are commonplace. I was referring to multiple transactions within a single request to be rare, and when it happens you don't necessarily want to share the same (read-only, isolation level) properties.
You do have a point that there is a use case for making multiple queries, without using a transaction, that you likely would want to share the same properties. However, my understanding is that isolation level is a meaningless concept without a transaction, and that leaves only read-only as the property of concern (for now?). It's not clear from the documentation whether the read-only property actually affects the other *sql.DB methods that take contexts; it only refers to BeginContext. I also don't think it's unwarranted to argue that if you want to conveniently ensure that multiple queries share the same properties that you can do so with a transaction. I understand that in rare circumstances the transaction would come with other, undesirable SQL semantics, but in those cases you might as well go through the trouble of dealing with this yourself. Either by passing the options to each query yourself, or to create some application-specific abstraction that handlesit for you. On Saturday, December 10, 2016 at 3:31:12 PM UTC+1, Daniel Theophanes wrote: > > > André, > > Thanks for the constructive feedback. I agree the signature you propose > would be another way to do this. > > For people who care about these settings, I would expect multiple queries > per request is normal and ensuring the props are the same sounds like a > benefit, not a detriment. In other words, I think you may be > underestimating how tied these are to a request. > > As another way of framing this, what do people have in their context Value > whitelist? -- 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.
