I need to write a specialized, embedded database for some .net Apps. The database开发者_StackOverflow part itself is no problem (as said, it\'s specialized), but the access to it from my .net code is.
I have a query, like such: var query = from sessions in dataSet where (names.Contains(sessions.Username))
I have users stored in a database that has latitude and longitude set on them. I want to write a filter method in my service layer.
When looking at a linked EntitySet<T> of a LINQ to SQL mapped entity, I see the following: I\'d like to see the following (achieved by using the .AsQueryable() extension method) so that I can
dataContext.Geo_Countries.Where(c => c.Name.Contains(searchKey)).ToList<Geo_Country>(); when the IQueryable returns no records, I get a value null except开发者_StackOverflowion.
For a project using LINQ to Entities 4.0, I have a setting in which I need to return a query with a (constant) value prepended.If I were coding it in SQL it would look something like this:
I\'ve got a list of IQueryable. I\'m trying to split this list into an array of IQueryable matching on a certain field (say fieldnum) in the first list...
I have an entity A with a simple navigation property B.For any given instance of A, we expect several related thousand instances of B.
I came across this post while I was looking for things to improve performance. Currently, in my application we are returning IList<> all over the place. Is it a good idea to change all of these
I\'m working on an IQueryable provider. In my IQueryProvider I have the following code: public TResult Execute<TResult>(Expression expression)