Query materialization after GroupBy leads to "unexpected" results

It is possible to change linq2db behavior to call Enumerable version on GroupBy internally when query materialize and GroupBy call is the last in sequence? I am requesting it, because in our project we already had several situations when developers write code like that:

var dict = db.Table.GroupBy(_ => _.SomeKey).ToDictionary(_ => _.Key, _ => _.ToList());

instead of

var dict = db.Table.AsEnumerable().GroupBy(_ => _.SomeKey).ToDictionary(_ => _.Key, _ => _.ToList());

I think this behavior reflects developer’s intension in more proper way.

I’ll send pull request with test for current behavior.

[MaceWindu]

More like a fix for #356

[filippobottega]

Configuration.Linq.GuardGrouping

Thank you! I needed to set Configuration.Linq.GuardGrouping = false. 👍