Incorrect search results

[fatg3erman]

The search results are a little strange.

Using the mpd frontend,
'search artist "Can"'
returns all tracks with 'can' in them - either the artist name, album name, or track name. This might just be a limitation of beets I think but can you confirm this?

Using the Mopidy HTTP frontend however, I get unusual results -
mopidy.library.search({artist: 'Can'}, ['beets:'])
returns an object with a uri property of 'beets:search-C', which contains every artist beginning with 'A', 'B', or 'C'.

Mopidy 0.14.2 (Ubuntu ppa), and the latest beets and mopidy-beets installed from pip (yesterday).

[fatg3erman]

Apologies, I was doing it wrong :) A quick perusal of the code revealed that I should be doing:
mopidy.library.search({artist: ['Can']}, ['beets:'])

[fatg3erman]

I'm reopening this because I found that the search results can be improved. Searching the way I put in my second comment does limit the results to 'Can' but it still returns every file which has the letters 'Can' in any metadata field, which is not too useful.

I've edited library.py to format the artist, album, track, and year queries according to the way the beet CLI tool does it:

        for (field, val) in query.iteritems():

            if field == "album":
                search.append('album:'+val[0])
            if field == "artist":
                search.append('artist:'+val[0])
            if field == "track":
                search.append('track:'+val[0])
            if field == "date":
                search.append('date:'+val[0])

This gives the results I'd expect.
You can still use mopidy's 'any' field to enter any generic search - eg year:2002

[sumpfralle]

thank you for your hint!
Now the search code should work fine for the different categories.