Skip to content

DBLinq will sometimes pick NoLanguageWords based on the order of discovering languages #343

@GoogleCodeExporter

Description

@GoogleCodeExporter
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.

Original issue reported on code.google.com by schlott1...@gmail.com on 26 Jul 2014 at 9:18

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions