False positive in ExpectationsWereMet

[jamiecuthill]

We have noticed a false positive problem when asking if the ExpectationsWereMet with MatchExpectationsInOrder = true, when expecting Exec calls against the database.

The problem is not in the order matching, but that outstanding expectations have not been satisfied.

Here is an example. Both the tests in sqlexec_test.go should be failing because RunExecs second call to Exec is not expected and as such one of our expected Exec calls has not been satisfied. The first test, where MatchExpectationsInOrder = true, is passing - it should not.

Tested on version 3769fed

---

We think the culprit is that the expectation matched in Exec has triggered = true before the query is matched. This currently happens on line 234. Moving this to just above line 251 resolves the issue.