hi jmeter_home/bin/jmeter.log should have logs - i dont think you have to give varchar(30) just varchar will do Finally have a debug sampler before your jdbc request so that you can see variables rae picked up - quotes arent needed for prepared statements
On Tue, Mar 25, 2014 at 3:52 PM, <[email protected]> wrote: > Hi all, > > I'm trying to setup JDBC insert sample, where I read data from CSV (using > "CSV Data Set Config"). > It works, if I use "Update statement", but fails for me for the "Prepared > update statement". > > My OK "Update statement" sample looks like this: > SQL Query: > insert into Master_non_p6spy > > (playerID,birthYear,birthMonth,birthDay,birthCountry,birthState,birthCity,deathYear, > > deathMonth,deathDay,deathCountry,deathState,deathCity,nameFirst,nameLast,nameGiven,weight,height,bats,throws,debut,finalGame,retroID,bbrefID) > > values > > ('${playerID}',${birthYear},${birthMonth},${birthDay},'${birthCountry}','${birthState}','${birthCity}',${deathYear},${deathMonth},${deathDay},'${deathCountry}','${deathState}','${deathCity}','${nameFirst}','${nameLast}','${nameGiven}',${weight},${height},'${bats}','${throws}','${debut}','${finalGame}','${retroID}','${bbrefID}'); > > However my failing "Prepared update statement": > SQL Query: > insert into Master_non_p6spy > (playerID) > values (?); > > Parameter values: ${playerID} > Parameter types: varchar(30) > > please note, that my sample csv row looks like this (the 1.st row is a > header one): > > playerID,birthYear,birthMonth,birthDay,birthCountry,birthState,birthCity,deathYear,deathMonth,deathDay,deathCountry,deathState,deathCity,nameFirst,nameLast,nameGiven,weight,height,bats,throws,debut,finalGame,retroID,bbrefID > aardsda01,1981,12,27,USA,CO,Denver,,,,,,,David,Aardsma,David > Allan,205,75,R,R,2004-04-06,2013-09-28,aardd001,aardsda01 > > Well, as far as I can see, the problem might be that values in csv are not > quoted (for strings/dates), still, I don't know how to workaround that > using "Prepared update statement". > > Btw: is there a way to see full exception logged for the failing JDBC > statement? As currently I just check the "Summary report" -> "% Failed" > column. > > Thanks. > > Peter Butkovic >
