This is an old one, I know, but it's something we really want from this tool (the advantages are clear) and we've actually already got a vaguely working prototype in place so I wanted to raise it here to see if anyone had experience with this that we could learn from before going deeper?
Essentially, the end goal is to allow the user to specify 'db' in place of 'csv' or 'xml' in the properties file - so long as valid connection details are given - and then JMeter would no longer use the jtl format but insert into a table. The problem as I see it is is that the listeners rely on the jtl format to work so if you redirect output to a new datasource then the listeners will no longer work so you're forced to create a new presentation layer. Any thoughts? @apc My hope is that synchronous db inserts would perform much better on a db vs. a file. Plus the advantages of having results stored in a db vs. lots of separate text files are huge. PS. Apologies, this post belongs in the dev forum but my subscription failed... ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/REPOST-Adding-an-option-to-output-results-to-a-db-not-csv-or-xml-tp5448528p5448528.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
