Only check inexact match when no exact match is found.

[yyjdelete]

Fix #39620

Avoid the exact match result be overwrite by later inexact ones.
This may not happen due to limited callsites, just make the code more clear.

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[dnfadmin]

All CLA requirements met.

[ghost]

Tagging subscribers to this area: @roji, @ajcvickers
See info in area-owners.md if you want to be subscribed.

[Wraith2]

Tests?

[yyjdelete]

Infact, I don't know how and where to create an test for this internal api. And maybe it's not a problem due to it's internal and there is no dupe tables with different case actually used by public apis.

https://github.com/dotnet/runtime/search?q=filename%3AMetaData.xml&unscoped_q=filename%3AMetaData.xml

[David-Engel]

I wouldn't close this PR just because you aren't adding tests. The bug is valid and benefits from being fixed, even though it doesn't surface with the existing *.SqlMetaData.xml embedded resources.

[danmoseley]

@cheenamalhotra this PR is pretty old now -- what's the next step?

[cheenamalhotra]

Since we don't have System.Data.SqlClient anymore, it can be closed.
The fix was ported over to Microsoft.Data.SqlClient - dotnet/SqlClient#668