Closed huturen closed 4 years ago
Hi @huturen since you are using pool.query
, you are not always using the same connection, which is why it continues to work after the error - because the pool will reconnect.
The error itself is coming from your MySQL server and this module is just surfacing the error. You'll need to consult whatever proxy software you are using to determine what that error means (sorry, I have never seen that error before).
If you think it's an issue with this module, let us know.
I get it now, thanks!
The error stack:
It seems that the connection was not closed or broken, because the other sqls after the caught error were executed correctly in the same connection:
INSERT INTO tbx (day,account) VALUES (20190927, 123) ON DUPLICATE KEY UPDATE day = 20190927,account = 123
was executed successfully.INSERT INTO tbx (day,account) VALUES (20190927,456) ON DUPLICATE KEY UPDATE day = 20190927,account = 456
caught error: ER_ACCESS_DENIED_ERROR: Proxy ERROR:connect to backend errorINSERT INTO tbx (day,account) VALUES (20190927,789) ON DUPLICATE KEY UPDATE day = 20190927,account = 789
was executed successfully.The three steps above are all in the same connection.
codes like below: