[0.6.0] Arguments mapped incorrectly in raw query

[abhinavc]

Hi Vitus,
Using the same example as in #223, I also noticed that arguments were being mapped positionally and not as per the names they were given in the query

So, the following in the DAO

@Query("update sports set rating = :rating, has_target = :hasTarget, "
      "num_results = :numResults where id = :id")
  Future<void> update(int id, int rating, bool hasTarget, int numResults);

results in the following

@override
  Future<void> update(
      int id, int rating, bool hasTarget, int numResults) async {
    await _queryAdapter.queryNoReturn(
        'update sports set rating = ? has_target = ? num_results = ? where id = ?',
        arguments: <dynamic>[id, rating, hasTarget, numResults]);
  }

The issue is with arguments. It should be arguments: <dynamic>[rating, hasTarget, numResults, id]

I have been assuming that the query string in DAO is parsed and the names of the arguments are used to find which goes where. Thus far, my queries have been simple, single-argument
queries. Hence this issue didn't show. But it did when I wrote my first multi-argument query.

Thanks
Abhinav.

[mqus]

This is roughly the same feature as #142 .

[jonasN5]

This is still an issue, lost an hour until I figured out I had to position the arguments according to the query usage order.