Comments on: Client-side properties and any remote LINQ provider

By: Damien Guard

Damien Guard — Wed, 12 Aug 2009 06:29:51 +0000

@BrianP, something simple like typeof(MyClass).ToString(); should cause it to be initialized.

[)amien

By: Summary 13.07.2009 « Bogdan Brinzarea’s blog

Summary 13.07.2009 « Bogdan Brinzarea’s blog — Mon, 13 Jul 2009 09:05:44 +0000

[...] Guard shows how to use client-side properties in LINQ remote queries eliminating the need to retrieve all the data from the server side and applying additional [...]

By: BrianP

BrianP — Sun, 28 Jun 2009 21:56:22 +0000

“The caveat to the usage technique shown above is you need to ensure your class has been initialized before you write queries to it. If this is a problem check out the usage considerations section below.”

I would like to keep the property expressions in the class itself, are there any other recommended ways of ensuring the class gets initialized before querying?

By: BrianP

BrianP — Sun, 28 Jun 2009 21:31:35 +0000

This is great! I can’t wait to try it out.

I agree with shawn, this should be standard part of linq.

By: The Technology Post for June 25th, 2009 | Nexo IT - Information Technology News

Fri, 26 Jun 2009 03:24:22 +0000

[...] ORM – Client-side properties and any remote LINQ provider – Damien Guard (Suggested by David Fowler) [...]

By: shawn

shawn — Fri, 26 Jun 2009 00:28:18 +0000

Nice, now that’s what I’m talking about! Any chance we can get something like this baked into the framework for 4.0? ;)

By: I love .NET! » Blog Archive » The Technology Post for June 25th, 2009

I love .NET! » Blog Archive » The Technology Post for June 25th, 2009 — Fri, 26 Jun 2009 00:00:09 +0000

[...] ORM – Client-side properties and any remote LINQ provider – Damien Guard (Suggested by David Fowler) [...]

By: Dew Drop – June 25, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop – June 25, 2009 | Alvin Ashcraft's Morning Dew — Thu, 25 Jun 2009 12:41:06 +0000

[...] Client-side properties and any remote LINQ provider (Damien Guard) [...]

By: KristoferA

KristoferA — Thu, 25 Jun 2009 03:02:46 +0000

This is *very* neat, thanks for the sample & the translation lib. This is at least as handy as System.Linq.Dynamic (which is one of my favorites :) ).

Just one note though: when used as the only discriminator in a where clause like in the full name example, SQL Server will be unable to use any indexes on the underlying fields. In other words, this is fine to use in projections, as ‘non-primary’ discriminators, or on small tables/result sets.

E.g. the fullname where clause will translate to something along the lines:
WHERE ((([t0].[Forename] + @p0) + [t0].[Surname]) LIKE @p1)
…and that basically tells SQL Server to concatenate forename + p0 + surname in all records in the table and then apply the like comparison…