Except, in the analysis, it isn't really a problem related to or caused by the ORM itself or the SQL it produces, it's a subtle issue invoked by implicit casting of types and collations, that could sneak in unobtrusively and unintentionally from anywhere.

And, throw in a subtle bug for a non-US English installs...

I think I've dealt with a similar issue with just straight up data loaded from different data sources...

VERY subtle bug.