JHunt , Thanks for your detailed reply. Appreciate your help.
As suggested I have written groovy script for this.
Here's a solution you could try, but it's pretty ugly.
Change your SQL to like this:
INSERT INTO db2admin1.cdaddrusagetp (${=
def aliases = [
"LangType": "LANG_TP_CD",
"AddUsageTp": "ADDR_USAGE_TP_CD",
// TODO
]
def columns = []
for (def prop: context.testStep.propertyList)
columns += prop.name != "ResponseAsXml" && prop.value != "NULL"
? aliases[prop.name]
: []
columns.join(', ')
}) VALUES (${=
def values = []
for (def prop: context.testStep.propertyList)
values += prop.name != "ResponseAsXml" && prop.value != "NULL"
? ":" + prop.name
: []
values.join(', ')
})
Here's the thing. We can write Groovy in the SQL request by using the ${= } syntax, but the syntax breaks down if we use brackets { } in the Groovy script. So above is not exactly how I'd prefer to write the script, but it doesn't have any brackets in it.
JHunt , Appreciate your help. Have tried your solution, but now it is not able to identify the parameters.
Throwing an error - "Error getting response; java.lang.IllegalArgumentException: Parameter 'LangType' was not found in the SQL Query. "
This continues for other variables as well.
Drat, this will be because all the TestStep properties are being added as properties to the PreparedStatement, so you can't leave out any of the properties from the query.
It looks like this is just a limitation of the JdbcRequestTestStep (which is quite limited) and trying to work around would just get even more complex.
At this point, if you want to send nulls. it is probably easier to write your own Groovy script that runs your INSERT statement instead of using JdbcRequestTestStep. You should be able to find posts on this forum or on Google for how to call the database in Groovy.
JHunt , Thanks for your detailed reply. Appreciate your help.
As suggested I have written groovy script for this.
