I may be crazy, or blind, but in your revised sample I don't see where
you're attempting to use 'new' within a .Where(), the only uses of
'where' I see are in DbLinqUserRepository.GetAll():
where u.Status == "active"
and in Program.Main():
var abe = userRepo.GetAll()
.Where(u => u.Name == "Abe").SingleOrDefault();
Both of these should be fine.
As an aside, be very careful about storing a DataContext in a class
member; it can be problematic (see the list archives).
Specifically, in both your examples you're comparing to a string, which
SHOULD work (and doesn't rely on ExpressionType.New) and is used
~everywhere in the unit tests, so I think your example is still omitting
something.
As for fixing quickly, there don't seem to be too many people working on
the project of late, so I'm not sure who you could ask.
As for fixing it yourself, I would suggest looking at
AnalyzeNewOperator() in
src/DbLinq/Data/Linq/Sugar/Implementation/ExpressionDispatcher.Analyzer.cs,
as that's what handles 'new' expressions within the .Select() extension
method support. You might be able to reuse/repurpose some of that logic
for use by .Where()...
- Jon
--
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en.
