The scope should be the same as any other variable i.e. it is available once
set.
>If, for example, I have two JDBC Request samplers in a
>given Thread Group, can I use a variable introduced in the first of the
>two JDBC samplers in specifying the query I want to issue in the 2nd of
>the two JDBC samplers?
Yes. it should work. Put a debug sampler after the first JDBC sampler and
verify the variables that got set.
I havent tried it , so the below is a guess
I think You should see varName1_1, varName1_2 etc as multiple values would
have got set.
You'd probably need a ForEach controller that iterates over varName and
returns into say x and use ${x} in your query.
regards
deepak
On Sun, Jan 10, 2010 at 5:36 PM, Mark Aronszajn <
[email protected]> wrote:
> I appreciate the introduction of assignable variables to handle values
> returned in result sets within JDBC Request Samplers.
>
> I also appreciate the later addition of documentation on how to
> introduce the variable names in the Variables field at the bottom of the
> JDBC Sampler dialogue.
>
> But it would be very helpful to include documentation on actual usage of
> such variables and also specification of the scope of those variables
> once introduced. If, for example, I have two JDBC Request samplers in a
> given Thread Group, can I use a variable introduced in the first of the
> two JDBC samplers in specifying the query I want to issue in the 2nd of
> the two JDBC samplers?
>
> An example of usage of such a variable would probably be sufficient. I
> tried just what I described above and it didn't work, perhaps because of
> the scope or perhaps for some other reason. I can't tell.
>
> I'd certainly appreciate any help on this issue in responses to this
> email.
>
> Thanks in advance,
>
