Issue 343 in dblinq2007: DBLinq will sometimes pick NoLanguageWords based on the order of discovering languages

[dblin...@googlecode.com]

Status: New
Owner: ----

New issue 343 by schlott1...@gmail.com: DBLinq will sometimes pick
NoLanguageWords based on the order of discovering languages
http://code.google.com/p/dblinq2007/issues/detail?id=343

Running under mono, reflection enumerates classes in a different order
to .NET.

The current implementation of DbLinq.Language.Implementation.Load returns
on the first suitable language.

When culture is 'en', the NoLanguageWords is the first language deemed
suitable, even though later through the enumeration it would have
found "EnglishWords" (When used by DbMetal).

NoLanguageWords should only be used as a fallback when no other suitable
language is found.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings