Currently, the xml results of JDBC test steps always include a rowNumber attribute for each row. This can cause problems with later validations that need to compare against the db results, because the validation is expecting that attribute to be identical in the data that you're later trying to compare against. (e.g. comparing json response data against a query of expected results.)
The rowNumber isn't part of the data, and we would never want that attribute to cause validation problems--it needlessly gets in the way, and is preventing us from simply using standard xQuery validations to check our API responses against expected results from a JDBC test step.
It would be very helpful if the JDBC test steps had a configuration option that let us tell it NOT to include the rowNumber attribute in the xml result.
Example:
Current:
<Results>
<ResultSet fetchSize="10">
<Row rowNumber="1">
<STATE>Alabama</STATE>
</Row>
<Row rowNumber="2">
<STATE>Alaska</STATE>
</Row>
<Row rowNumber="3">
etc...
Desired, by configuration:
<Results>
<ResultSet fetchSize="10">
<Row>
<STATE>Alabama</STATE>
</Row>
<Row>
<STATE>Alaska</STATE>
</Row>
<Row>
etc...