Fork me on GitHub
erre lin05:02:16

Hi, I asked this question in the beginner channel and was suggested asking it here. seancorfield already advises using next.jdbc feature to keep a connection pool. I'm just wondering what's happening on the HugSQL side? Thank you in advance.


HugSQL does not control the connection. Rather, each adapter passes the connection object (which can be a db spec, a db connection, a db connection pool, or a transaction object) down to the underlying library.