Type specific method interpretation

Description

Currently method calls are interpreted according to their names, not types+names. So that a call like this
var results=from f in session.Linq<Customer>()
where f.Average()>10
select f;

is interpreted as if f were a list. This shouldn't be like this.

I think there is a necessity of introducing
IMethodTranslator's which will translate the method calls accordingly.

Environment

None

Assignee

Unassigned

Reporter

Tuna Toksoz

Labels

None

Components

Affects versions

Priority

Critical
Configure