Usage of pool.getConnection() vs pool.query()

[ddluc]

I'm trying to understand the pros / cons of using pool.getConnection() over pool.query().

From Issue #1202 I gathered that pool.query is essentially a shortcut for pool.getConnection(), connection.query() and connection.release(). So it would appear advantageous to just query the pool directly in most cases. The only major scenario where using pool.getConnection() might be beneficial is if you needed to execute a series of queries at once.

[sidorares]

yes, exactly what you explained yourself. getConnection if you need transactions or some state between queries

[sidorares]

two calls to pool.query() likely will happen in two separate connections ( and in parallel )

[ddluc]

Thanks for the timely response! What are your thoughts on adding that info to this section of the docs? (Unless I'm just missing it)

[sidorares]

I think it would be helpful for many

[ddluc]

OK great -- I'll create a pull request once I'm wrapped up with what I'm working on.

[borekb]

The info here is very useful, I've created a PR which tries to incorporate it into README: #2031