You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2008/02/27 13:45:35 UTC
[Bug 40934] CSV Data Set Config parameters cannot be used in some
Config elements
http://issues.apache.org/bugzilla/show_bug.cgi?id=40934
Nikolai Prokoschenko <ni...@prokoschenko.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nikolai@prokoschenko.de
--- Comment #4 from Nikolai Prokoschenko <ni...@prokoschenko.de> 2008-02-27 04:45:34 ---
So this bug is actually about JDBC sampler, right? Judging from mailing list
traffic and own experience, it's the only sampler that doesn't support
user-defined variables. Considering this bug didn't exist in the "old" JDBC
sampler (e.g. in 2.0.1) it is introduced in 2.3 and is making life difficult
for people like myself who have to migrate from 2.0.1
I'm having the same problems: variables in JDBC configuration field are not
used, i.e. replaced with blanks. Using verbatim configuration in these fields
works, using properties on the command line works too, but not variables with
values calculated at run-time.
If this is really a problem with initialization order (which it seems it is),
could some developers please take a look the JDBC sampler and make it use the
runtime configuration? I tried to, but my experience is limited and JMeter code
is foreign to me.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org