The problem of node operation mysql querying the corresponding columns according to id

make a list of articles, and then enter the details according to the id of the article.
now I have a problem, that is, when my article list jumps to article details according to id, the article details get id and then look up the corresponding columns according to id.
you can see that my output sql statement has two different id, but both are the same variable. The first output is dynamic, while the second is always the id, checked for the first time. Why?
now I can only get the id column of the first click, and click on other articles to get the id of the first click.

Javascript node.js mysql

Mar.10,2021

The problem of

is the problem of function callbacks. Why do you want to do routing nesting? The req and res of the two requests are different, and coupled with the calling mechanism of the javascript callback function, the sql variables will overlap.

Previous: How to use domain-driven design (DDD) correctly?

Next: RUN npm run build has been stuck in Dockerfile.

About the problem of mySQL connection
first of all, the system uses the manjaro (linux) system. I installed mySQL, in the project directory, but when I node timetrack_server.js the file, I made the following error: home dema codeSpace studyNode testMySQL timetrack_server.js:49 if ...

Javascript node.js mysql

Jan.31,2022