When selecting a column produced by a string concatination the resulting SQL is invalid.
Consider following VB.net code:
The resulting SQL is
This statement produces an error Conversion failed when converting the varchar value 'Chauseestrasse 3' to data type int.
To get a valid SQL I've to write my query like
Please implement a recognition of those operations to always create the "conversion" SQL.
Note: This affects both VB.NET and C# statements.
See BinaryExpressionSqlBackendIntegrationTest.StringConcatenation for a sample of the wrong behavior. It looks like the integration test missed this as being not the correct /intended behavior.
Likely, there is a second problem in the re-linq frontend's partial evaluation: when concatenating a const int to a string property, the conversion is lost in the querymodel's select expression. The conversion still exists when concatenating properties, not that it helps much.