We're updating the issue view to help you get more done. 

Some Linq statements generate incorrect AS <alias> suffixes

Description

Examples, based on some DomainObject TestProduct, which has a persistent string property ProductName.

Will fail

Working

Will fail

Activity

Show:
Michael Ketting
December 10, 2015, 4:33 PM
Edited

Analysis: The problem is in distinguishing if the NamedExpression is currently being used in an argument or as a value in a projection. Aliases are only allowed inside projections.

Michael Ketting
December 10, 2015, 4:37 PM

Status quo:

  • SqlGeneratingOuterSelectExpressionVisitor.VisitSqlConvertedBoolean already re-wraps the NamedExpression.

Assignee

Michael Ketting

Reporter

Michael Walk

Labels

None

Components

Fix versions

Priority

Normal
Configure