Connection Pool Use Skips Function Body












0















I am a complete Node noob and I am struggling to understand why, when this function is called, the entire execution of the method is skipped. If I follow along in the debugger, I literally see execution go from the first line (the function declaration) to the last line, without hitting anything in between.



Thank you very much! Honestly, I'm really struggling to understand the async/await nature of Node code, so if you also have any good resources on working through that, I would greatly appreciate it.



var mysql = require('mysql');

var connPool = mysql.createPool({
host: "secret",
user: "secret",
password: "secret"
});

...
There is code executing here that eventually calls the function below
...

function getOrgAndAgentId(emailAddress){
connPool.getConnection(function(err, conn){
if(err){
console.log(err);
return;
}

var sql = getAgentIdAndOrgIdSql(emailAddress);
conn.query(sql, , function(err, result){
conn.release();
if(err){
console.log("TPM Query Error: " + err)
return;
}

var ret = {
agentId: result.row[0][agentIdAndOrgIdEnum.agentId],
orgId: result.row[0][agentIdAndOrgIdEnum.orgId]
}

return ret;
});
});
}









share|improve this question























  • It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

    – Connor
    Nov 29 '18 at 18:25
















0















I am a complete Node noob and I am struggling to understand why, when this function is called, the entire execution of the method is skipped. If I follow along in the debugger, I literally see execution go from the first line (the function declaration) to the last line, without hitting anything in between.



Thank you very much! Honestly, I'm really struggling to understand the async/await nature of Node code, so if you also have any good resources on working through that, I would greatly appreciate it.



var mysql = require('mysql');

var connPool = mysql.createPool({
host: "secret",
user: "secret",
password: "secret"
});

...
There is code executing here that eventually calls the function below
...

function getOrgAndAgentId(emailAddress){
connPool.getConnection(function(err, conn){
if(err){
console.log(err);
return;
}

var sql = getAgentIdAndOrgIdSql(emailAddress);
conn.query(sql, , function(err, result){
conn.release();
if(err){
console.log("TPM Query Error: " + err)
return;
}

var ret = {
agentId: result.row[0][agentIdAndOrgIdEnum.agentId],
orgId: result.row[0][agentIdAndOrgIdEnum.orgId]
}

return ret;
});
});
}









share|improve this question























  • It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

    – Connor
    Nov 29 '18 at 18:25














0












0








0








I am a complete Node noob and I am struggling to understand why, when this function is called, the entire execution of the method is skipped. If I follow along in the debugger, I literally see execution go from the first line (the function declaration) to the last line, without hitting anything in between.



Thank you very much! Honestly, I'm really struggling to understand the async/await nature of Node code, so if you also have any good resources on working through that, I would greatly appreciate it.



var mysql = require('mysql');

var connPool = mysql.createPool({
host: "secret",
user: "secret",
password: "secret"
});

...
There is code executing here that eventually calls the function below
...

function getOrgAndAgentId(emailAddress){
connPool.getConnection(function(err, conn){
if(err){
console.log(err);
return;
}

var sql = getAgentIdAndOrgIdSql(emailAddress);
conn.query(sql, , function(err, result){
conn.release();
if(err){
console.log("TPM Query Error: " + err)
return;
}

var ret = {
agentId: result.row[0][agentIdAndOrgIdEnum.agentId],
orgId: result.row[0][agentIdAndOrgIdEnum.orgId]
}

return ret;
});
});
}









share|improve this question














I am a complete Node noob and I am struggling to understand why, when this function is called, the entire execution of the method is skipped. If I follow along in the debugger, I literally see execution go from the first line (the function declaration) to the last line, without hitting anything in between.



Thank you very much! Honestly, I'm really struggling to understand the async/await nature of Node code, so if you also have any good resources on working through that, I would greatly appreciate it.



var mysql = require('mysql');

var connPool = mysql.createPool({
host: "secret",
user: "secret",
password: "secret"
});

...
There is code executing here that eventually calls the function below
...

function getOrgAndAgentId(emailAddress){
connPool.getConnection(function(err, conn){
if(err){
console.log(err);
return;
}

var sql = getAgentIdAndOrgIdSql(emailAddress);
conn.query(sql, , function(err, result){
conn.release();
if(err){
console.log("TPM Query Error: " + err)
return;
}

var ret = {
agentId: result.row[0][agentIdAndOrgIdEnum.agentId],
orgId: result.row[0][agentIdAndOrgIdEnum.orgId]
}

return ret;
});
});
}






mysql node.js






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 '18 at 22:18









jhammondjhammond

6931821




6931821













  • It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

    – Connor
    Nov 29 '18 at 18:25



















  • It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

    – Connor
    Nov 29 '18 at 18:25

















It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

– Connor
Nov 29 '18 at 18:25





It's not skipped; it's just an asynchronous function call, so your surrounding logic proceeds without waiting for it to complete. See also: stackoverflow.com/a/14220323/2301088

– Connor
Nov 29 '18 at 18:25












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53528953%2fconnection-pool-use-skips-function-body%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53528953%2fconnection-pool-use-skips-function-body%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

count number of partitions of a set with n elements into k subsets

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks