chrisjj wrote:Your continued obfuscation of these issues is not constructive.

I never said that path search does work, it doesn't for me either.

An update shows that "" will do full word matches, which doesn't take away that "fullpath" should find the track. I assume this is caused by how special characters are handled.

> I keep having to explain the same thing to you in every topic.

You are mistaken.

> As indicated by Ludek "A" will only find those fields with value A nothing more nothing less.

Sorry, but once again, this is wrong. I have already reported this failure of program behaviour to accord in the Path case, and it is logged in Mantis.

Your continued obfuscation of these issues is not constructive.

Please take the time to read through all your posts and the bug's attached to it. This is the reason to post in the same topic as now I keep having to explain the same thing to you in every topic.

The fact that "" finds certain results with leading/trailing space doesn't mean it's how "" works. As indicated by Ludek "A" will only find those fields with value A nothing more nothing less. From that you can derive that the current behavior where it will also find partial matches when value in field as leading/trailing spaces might not be intentional.
That's why now in various of your topics on this issue I proposed to wait for a developer response to clarify if full match means full field or full word match. Based on that information further testing can give us answers on any existing bugs on this feature.

> "" only returns full matches not partial matches.

Do make your mind up, Lowlander! Previously you said "It does find partial matches as long as partial matches have a space leading/trailing".

EDIT:
> That should work and doesn't.

Then please file this as a bug. Someone has marked this thread BUG#5186 whereas http://www.ventismedia.com/mantis/view.php?id=5186 is titled "Viewing Issue Simple Details" and the description makes no mention of this bug.

As you opened so many topics on this I didn't see this one included the full path in double quoutes search issue. That should work and doesn't.

Lowlander wrote:[Actually yours is not a bug as] "" only returns full matches not partial matches.

Untrue e.g. quick search for a full path fails to match.

Actually yours is not a bug as "" only returns full matches not partial matches. I did ask for a method to do a search like .wma and get all WMA files returned.

Of course the specific extension search could be solved by allowing to search the Type field in the Quick Search (like it's possible in the Advanced Search).

Lowlander wrote:The path issue might be because of different bug though.

Well, quite. I'd appreciate it if you would file the bug I reported, not conflating it with any other bug that may or may not be different.

Strange as "Madonna" does find Madonna as artist.

The path issue might be because of different bug though.

Lowlander wrote:Added as Mantis Bug 5186

Thanks, but the characterisation is in error:

When using the quick search with "" MediaMonkey expects that the search results containing a leading/trailing space or no character.

The "no character" qualification does not accord with the case of query = full path i.e. S:\TLIB\02480002928829\1\16.wma still fails to match that Path.

They didn't as it's my opinion not theirs.

Lowlander wrote:These are just small bugs

How did the test team measure the size of a bug it never found, I wonder...

These are just small bugs, no data is being corrupted or lost. The new search has many test cases that need to be run and thus errors can occur. This is stuff that comes up in beta tests.

Added as Mantis Bug 5186

Crikey. How this new search engine passed alpha test, GOK!