AddSeconds not being linqified through to db query

Hi,  running this query against a db.

unitOfWork.Find<Entity>().Where(j => (j.Status == JobStatus.Queued || j.Status == JobStatus.Processing || j.Status == JobStatus.Requeued) &&
                                                                                        j.CreatedOn.AddSeconds(j.UserInitiatedOperation.TimeoutSeconds) < DateTime.UtcNow).ToList()

When i run sql profiler i see it's not converting DateTime.AddSeconds into the db query - so it's pulling back a very large resultset each time...

I was expecting that DateTime.AddSeconds (even if it's two entity properties being referenced such as EntityPropertyAValue.AddSeconds(EntityPropertyBValue)) would happily translate through to sql... yes?

cheers
justin

Are you on a recent build?  We added support for this in the 18 September nightly (build 14820).  If you're on this build or later, what database are you using?

we're on 29 Sep build.

running against sql 2k8R2

i'll fire you through the model, query and sql trace if you like...

Ah... hadn't noticed that the argument to AddSeconds() involved traversing an association.  That's not currently supported as far as I know.  (In fact when I try it I get an error rather than an unfiltered query.)

Hi Justin,

Just as an additional comment here, you are not actually running a server side LINQ query - the initial call is Find<Entity>() which is going to pull in the full set of that type into memory, the LINQ query is being run client side over the resulting objects - the profiler trace you are seeing matches up with that.

Run this as UnitOfWork.UserInitiatedJobs.Where(...) instead - you will then likely run into the issue which Ivan indicated above.

Jeremy

thanks for spotting that - must have been a very late night when i wrote that 'find' in.

so as per ivan's comment - is this something you're looking to include in a future build?