Fix ResultWrapper handling for non-prepared statements

[ng-galien]

In order to fix #3008

[ng-galien]

@vlsi I did not align all the test because I'm not sure this is the expected behavior.
I mainly apply SET handling only on prepared statements.
When specs for expected results are ok I will finish the job.

[olavloite]

In order to fix #3008

@ng-galien I think you meant to reference #3007

[ng-galien]

In order to fix #3008

@ng-galien I think you meant to reference #3007

My bad

[ng-galien]

@olavloite
I think all tests related to inlining SET in Statement, except yours, can be removed as it should only affect PreparedStatement.

[olavloite]

`

@olavloite I think all tests related to inlining SET in Statement, except yours, can be removed as it should only affect PreparedStatement.

I don't quite understand what you mean with that:

1. If your change only affects PreparedStatement, then any existing test for Statement can remain, as they should be unaffected.
2. If the tests using Statement are failing, then it would seem to me that the assumption that it only affects PreparedStatement is wrong.

Or am I misunderstanding what you mean?

[ng-galien]

@olavloite there was not existing test for combining SET and statement. New ones where aligned with the unexpected behavior you related in the issue.