[ http://issues.apache.org/jira/browse/BEEHIVE-868?page=all ]
matt c closed BEEHIVE-868. -------------------------- Verified fix using revision 417573M. Verified by modifying and running existing system-controls test (uses ResultsTestCtrl.jcx). Verified in another environment as well. > Calling stored proc with uppercase 'CALL', and providing SQLParameter > arguments, results in a compiler error > ------------------------------------------------------------------------------------------------------------ > > Key: BEEHIVE-868 > URL: http://issues.apache.org/jira/browse/BEEHIVE-868 > Project: Beehive > Issue Type: Bug > Components: System Controls > Reporter: Chad Schoettger > Assigned To: matt c > Priority: Minor > Fix For: 1.0.1 > > Attachments: BEEHIVE-868.diff > > > When trying to call SP's via the JdbcControl, and sending SQLParameters as > arguments, a compile time error will be thrown if the 'CALL' part of the > statement is in uppercase. The statement works fine if lowercase 'call' is > used instead. It could be that this is a side-effect of the special > processing of the statement that is done because of the presence of the > SQLParameter argument. > Error: > org.apache.beehive.controls.api.ControlException: Error parsing SQL > statment.Encountered " " at line 1, column 6. > [apt] Was expecting one of: > [apt] "}" ... > [apt] "|" ... > [apt] [Encountered " " at line 1, column 6. > [apt] Was expecting one of: > [apt] "}" ... > [apt] "|" ... > [apt] ] > [apt] public void callSP_name_city(SQLParameter[] sqlParameters) throws > SQLException; > Workaround: > Only use lowercase 'call' when accessing SP's with SQLParameters. > Repro: > Call a SP, providing a SQLParameter as an argument, and use an uppercase > 'CALL' as part of the statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
