Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unprepare execute on pool

See original GitHub issue

const info = await db.promisePool.execute(query2,updateArr);
        if(info[0].affectedRows){
            db.promisePool.unprepare(query2);

TypeError: _dbcontroller.default.promisePool.unprepare is not a function

Issue Analytics

State:
Created 4 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

thibaudscommented, May 16, 2022

Yes, number of clients times maxPreparedStatements in each client config should give you a possible maximum number of prepared statements clients can attempt to create simultaneously

That is exactly what we used thanks to your replies 😃 I guess you can close this old issue that I shamelessly used. Thanks again.

1reaction

sidorarescommented, May 16, 2022

Maybe the cache eviction mechanism cannot keep up with the speed of insertions?

statement.close() unfortunately does not have success/error confirmation at the protocol level, so the client expects the PS to be unprepared as soon as “close statement” command is sent. I can potentially see some out of sync situation here

Yes, number of clients times maxPreparedStatements in each client config should give you a possible maximum number of prepared statements clients can attempt to create simultaneously