José Nieto

As far as I understand, defaulting to `0` means connections will be reused: https://golang.org/pkg/database/sql/#DB.SetConnMaxLifetime Do you currently have any problems with short-lived sessions?

Now that the query builder supports query expansion we can add `Union()/UnionAll()` methods to the builder and do something like: ```go sel1 := sess.SelectFrom()... sel2 := sess.SelectFrom()... sess.Union(sel1, sel2) ```

I think we can make this work with `db.Result` too, as you suggested @VojtechVitek. Let's do both.

Oh! CGO-free, that's good news. We've recently replaced the PostgreSQL driver, it was not that straightforward because PostgreSQL offers many different features and types (like JSON, ARRAY, etc). sqlite offers...

Hi @uynap, this should not be a problem, you can use `$n` or a list of `?` placeholders too.

Hmm, good question. There's currently nothing in place that gives you this when using a result set, you could count matches before updating (within a transaction) but that's not always...

I think this is possible with `database/sql`'s `RowsAffected()` without any additional operation, the problem here is that, as far as I know, this depends on the database, MongoDB doesn't have...

Hello @dc0d, sorry for the delay! I think you're right, we should explain about RowsAffected, I'll keep this issue open until providing docs for that. Sessions are concurrent safe, you...

Quick update: things are looking good with pgx, a few tests are going to be changed but in general seems like it won't be problematic to adopt it for both...

Hello @coolerfall, I could not replicate this issue, I added an additional test for the paginator here: https://github.com/upper/db/pull/609 Could you provide more data on how to replicate?