Why does this procedure work on the console but not with JDBC on NetBeans?
I did this stored procedure to save myself time (and memory) by creating procedures for the tables of a school assignment.
CREATE PROCEDURE consultar (IN tableName VARCHAR(40))
BEGIN
SET @t1 = CONCAT('SELECT * FROM ', tableName);
PREPARE stmt3 FROM @t1;
EXECUTE stmt3;
DEALLOCATE PREPARE stmt3;
END//
When I try it through the MySQL console it gives me the expected result, but when I run it in a query of a Java project in NetBeans with JDBC, I take the parameter of the procedure as a column to consult.
CALL consultar("mytablename");
GRAVE: Query could not be performed
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'mytablename' in 'field list'
I gave several turns to the matter and I can not understand why this happens. Thank you in advance.
java mysql stored-procedures netbeans
asked Nov 13 '18 at 2:20
LuuisLuuis
11
add a comment |
I did this stored procedure to save myself time (and memory) by creating procedures for the tables of a school assignment.
CREATE PROCEDURE consultar (IN tableName VARCHAR(40))
BEGIN
SET @t1 = CONCAT('SELECT * FROM ', tableName);
PREPARE stmt3 FROM @t1;
EXECUTE stmt3;
DEALLOCATE PREPARE stmt3;
END//
When I try it through the MySQL console it gives me the expected result, but when I run it in a query of a Java project in NetBeans with JDBC, I take the parameter of the procedure as a column to consult.
CALL consultar("mytablename");
GRAVE: Query could not be performed
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'mytablename' in 'field list'
I gave several turns to the matter and I can not understand why this happens. Thank you in advance.
java mysql stored-procedures netbeans
asked Nov 13 '18 at 2:20
LuuisLuuis
11
The fact the ereror is reporting thatmytablenameis being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included insql_mode. As a test, I would use single quotes instead of double quotes around the string literal ...CALL consultar('mytablename'). (I think the error is being thrown on theCALLstatement, before it even gets to executing the procedure. With JDBC, we'd be using aCallableStatementto execute a stored procedure.
– spencer7593
Nov 13 '18 at 2:27
add a comment |
I did this stored procedure to save myself time (and memory) by creating procedures for the tables of a school assignment.
CREATE PROCEDURE consultar (IN tableName VARCHAR(40))
BEGIN
SET @t1 = CONCAT('SELECT * FROM ', tableName);
PREPARE stmt3 FROM @t1;
EXECUTE stmt3;
DEALLOCATE PREPARE stmt3;
END//
When I try it through the MySQL console it gives me the expected result, but when I run it in a query of a Java project in NetBeans with JDBC, I take the parameter of the procedure as a column to consult.
CALL consultar("mytablename");
GRAVE: Query could not be performed
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'mytablename' in 'field list'
I gave several turns to the matter and I can not understand why this happens. Thank you in advance.
java mysql stored-procedures netbeans
asked Nov 13 '18 at 2:20
LuuisLuuis
11
I did this stored procedure to save myself time (and memory) by creating procedures for the tables of a school assignment.
CREATE PROCEDURE consultar (IN tableName VARCHAR(40))
BEGIN
SET @t1 = CONCAT('SELECT * FROM ', tableName);
PREPARE stmt3 FROM @t1;
EXECUTE stmt3;
DEALLOCATE PREPARE stmt3;
END//
When I try it through the MySQL console it gives me the expected result, but when I run it in a query of a Java project in NetBeans with JDBC, I take the parameter of the procedure as a column to consult.
CALL consultar("mytablename");
GRAVE: Query could not be performed
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'mytablename' in 'field list'
I gave several turns to the matter and I can not understand why this happens. Thank you in advance.
java mysql stored-procedures netbeans
java mysql stored-procedures netbeans
asked Nov 13 '18 at 2:20
LuuisLuuis
11
asked Nov 13 '18 at 2:20
LuuisLuuis
11
asked Nov 13 '18 at 2:20
LuuisLuuis
11
asked Nov 13 '18 at 2:20
LuuisLuuis
11
asked Nov 13 '18 at 2:20
LuuisLuuis
11
11
The fact the ereror is reporting thatmytablenameis being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included insql_mode. As a test, I would use single quotes instead of double quotes around the string literal ...CALL consultar('mytablename'). (I think the error is being thrown on theCALLstatement, before it even gets to executing the procedure. With JDBC, we'd be using aCallableStatementto execute a stored procedure.
– spencer7593
Nov 13 '18 at 2:27
add a comment |
The fact the ereror is reporting thatmytablenameis being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included insql_mode. As a test, I would use single quotes instead of double quotes around the string literal ...CALL consultar('mytablename'). (I think the error is being thrown on theCALLstatement, before it even gets to executing the procedure. With JDBC, we'd be using aCallableStatementto execute a stored procedure.
– spencer7593
Nov 13 '18 at 2:27
The fact the ereror is reporting that
mytablename is being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included in sql_mode. As a test, I would use single quotes instead of double quotes around the string literal ... CALL consultar('mytablename'). (I think the error is being thrown on the CALL statement, before it even gets to executing the procedure. With JDBC, we'd be using a CallableStatement to execute a stored procedure.– spencer7593
Nov 13 '18 at 2:27
The fact the ereror is reporting that
mytablename is being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included in sql_mode. As a test, I would use single quotes instead of double quotes around the string literal ... CALL consultar('mytablename'). (I think the error is being thrown on the CALL statement, before it even gets to executing the procedure. With JDBC, we'd be using a CallableStatement to execute a stored procedure.– spencer7593
Nov 13 '18 at 2:27
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272838%2fwhy-does-this-procedure-work-on-the-console-but-not-with-jdbc-on-netbeans%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
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272838%2fwhy-does-this-procedure-work-on-the-console-but-not-with-jdbc-on-netbeans%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
The fact the ereror is reporting that
mytablenameis being interpreted as a column name rather than a string literal, that makes me think that MySQL connection has ANSI_QUOTES included insql_mode. As a test, I would use single quotes instead of double quotes around the string literal ...CALL consultar('mytablename'). (I think the error is being thrown on theCALLstatement, before it even gets to executing the procedure. With JDBC, we'd be using aCallableStatementto execute a stored procedure.– spencer7593
Nov 13 '18 at 2:27