Summary: | Allow to assign the OUT result of a JDBC CALLABLE to JMeter variables | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Roman Bargezi <rbargezi> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | p.mouawad |
Priority: | P2 | ||
Version: | 2.6 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: |
Proposed enhancement patch to Rev 1234407 of AbstractJDBCTestElement.java
Proposed enhancement patch to Rev 1234407 of AbstractJDBCTestElement.java |
Description
Roman Bargezi
2012-04-13 10:35:02 UTC
Created attachment 28602 [details]
Proposed enhancement patch to Rev 1234407 of AbstractJDBCTestElement.java
Created attachment 28603 [details]
Proposed enhancement patch to Rev 1234407 of AbstractJDBCTestElement.java
Hello, Thanks for the patch but either I didn't fully understand its behaviour or there is something wrong in it. Particularly in the way you use the variables from JMeterContext. Aren't you making suppositions on the order and number of variables being equals to number of OUT parameters. I think there is some information missing, maybe there should be an additional field or the result variable should be a COMMA separated variable names. Regards Hi, the intent of the code is to store the OUT results in the variables provided to the "Variable Names" field in a similar manner as it is currently used to store results returned by a select statement but without generating new numerated versions of the variables. The variable names should be comma separated and in the same sequence as the OUT parameters returned by the call. If there are less variable names than OUT parameters only as many results shall be stored in the thread-context variables as variable names were supplied. If more variable names than OUT parameters exist, the additional variables will be ignored. As such, I am making assumptions about the sequence and the number of variable names provided. Looking at the code that is used for storing results of a SELECT statement, this seems to be the case here as well. I checked the code once more (and also tested it in our environment) and it seems to be doing what above description intends. Thanks for clarification and patch. Patch applied. Date: Tue Apr 24 11:35:34 2012 New Revision: 1329645 URL: http://svn.apache.org/viewvc?rev=1329645&view=rev Log: Bug 53073 - Allow to assign the OUT result of a JDBC CALLABLE to JMeter variables Modified: jmeter/trunk/src/protocol/jdbc/org/apache/jmeter/protocol/jdbc/AbstractJDBCTestElement.java jmeter/trunk/xdocs/changes.xml jmeter/trunk/xdocs/usermanual/component_reference.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2808 |