The question is: Given a database backend that understands LeftStr and RightStr: where, in a custom ADO.NET provider implementation, would I establish a mapping to the immutable EDM canonical functions Left and Right?
So I am working with the SQLite ADO.NET provider and it works, more or less, until you bump up against some string functions that are present but named differently. Amongst the missing/mismapped functions are the canonical string functions Left and Right.
In the SQLite extension the equivalent functions are mapped to LeftStr and RightStr.
I have come up short when looking for information. Lacking documentation for this scenario, or my lack of ability in finding it, I have step traced the call all the way into the factory method that creates the command with the generated SQL and suspect that the SemanticResolver is my best clue, but I have taken a few stabs in the dark by fudging with the only exposed seam I can find, ProviderManifest.xml, but am having no joy.