Closed Galienna closed 2 years ago
i'm trying to reproduced the problem without success. Do you have any additional information ? could you confirm that those event are set with poll 'connection' event, then connection 'error' event ? something like :
pool.on('connection', conn => {
conn.on('error', (err) => {
console.log(`connection ${conn.threadId} error `);
console.log(err);
})
});
corrected with https://jira.mariadb.org/browse/CONJS-196. Will be part of 3.0.1 release
Hi,
The 3.0.0 release seems to have introduced a bug that wasn't there in 2.5.6.
Scenario
Exact same code and scenario works fine with 2.5.6
Good luck and thank you for the lib :)