Releasing connections

Hello,
In the documentation, the way to release a connection from the pool is to use the callback version of getting a connection.

pool.getConnection(function(err, conn) {
   // Do something with the connection
   conn.query(/* ... */);
   // Don't forget to release the connection when finished!
   pool.releaseConnection(conn);
})

By looking at the source code, I noticed that the promisified pool implementation did not have releaseConnection implemented, which explains the code example in README.

Because I dont want to deal with callback after finding, this lib this seems like one of the only callback methods left. I wanted to find a work around without any wrapper. And, I was able to come up with this.

const poolPromise = pool.promise()
var connection = await poolPromise.getConnection()
await connection.beginTransaction()
// couple queries
await connection.commit()
connection.release()

Is there any downside to releasing the connection directly and bypassing the pool's release method?

Start with the README connection examples and the promisified pool implementation mentioned in the issue, then compare how callback and promise connections are released. Done means the supported release behavior is clarified and the documentation no longer leaves the promisified API ambiguous.