Oops, we did it again

re: Oops, we did it again

thomas woelfer — Thu, 11 May 2006 03:10:47 GMT

Matt,

this stuff is so cool. linq rocks...

WM_THX
thomas woelfer

re: Oops, we did it again

ransom — Thu, 11 May 2006 03:54:54 GMT

OMG! This is so cool. I don't know what it is, but it is so cool.

re: Oops, we did it again

Marc Brooks — Thu, 11 May 2006 04:18:49 GMT

Show me how that last one can be parameterized to avoid injection issues...

re: Oops, we did it again

mattwar — Thu, 11 May 2006 04:44:51 GMT

You wouldn't use that text based filter if you were assembling user input with other pieces, you'd use the node construction pattern. The text based filter would only be used if the entire predicate is supplied by the user. The user cannot cause injection because this expression is parsed, turned into expression nodes that must statically check as a correct predicate. DLINQ automatically converts the user supplied literal into an ADO.Net parameter, so there is no injection on that end either.

Linq May CTP released - and info on Query Trees and IQueryable

yag: Community and Architecture — Thu, 11 May 2006 17:57:31 GMT

I mentioned this in my last blog entry, but thought I should make it more discoverable. We've released...

Linq May CTP released - and info on Query Trees and IQueryable

yag: Community and Architecture — Thu, 11 May 2006 17:58:33 GMT

I mentioned this in my last blog entry, but thought I should make it more discoverable. We've released...

LINQ May CTP

Pedro Felix — Thu, 11 May 2006 19:43:36 GMT

A new LINQ CTP is available. Looking for a reason to install it? See&nbsp;this.

re: Oops, we did it again

mikep — Fri, 12 May 2006 06:20:00 GMT

Matt, introduction of IQueriable<T> seams a logical step to bridge different linq implementations of PDC timeframe. It seams next step would make explicit IEnumerable<T> based query operators implementation not necessary?! What do you think?

re: Oops, we did it again

mattwar — Fri, 12 May 2006 07:16:54 GMT

It would seem that you don't need IEnumerable<T> operators at all anymore. However, you still need them as actual methods to invoke when the IQueryable<T> is executed locally, and its has additional overhead due to the expression tree representation and the runtime compilation.

New LINQ CTP, Awesome New Features

hacked.brain — Fri, 12 May 2006 07:49:59 GMT

LINQ CTP May 2006

Impersonation Failure — Fri, 12 May 2006 12:01:00 GMT

There's an update to the LINQ extensions for the .NET framework available on MSDN. Check it out on...

Why wait when you can have it now?

Mike Griffin — Fri, 12 May 2006 18:18:19 GMT

See (scroll down to the bottom for better samples)

http://www.entityspaces.net/portal/Documentation/QueryAPISamples/tabid/80/Default.aspx

Anyway, LINQ looks very cool Matt, what level are you involved with it?

For Discusssion?

Mike Griffin — Fri, 12 May 2006 18:21:09 GMT

AggregateTestCollection aggTestColl = new AggregateTestCollection();
aggTestColl.Query.es.CountAll = true;
aggTestColl.Query
.Select (aggTestColl.Query.IsActive,
aggTestColl.Query.DepartmentID)
.Where (aggTestColl.Query.IsActive.Equal(true))
.GroupBy(aggTestColl.Query.IsActive,
aggTestColl.Query.DepartmentID)
.OrderBy(aggTestColl.Query.DepartmentID.Ascending, aggTestColl.Query.IsActive.Ascending);
aggTestColl.Query.es.WithRollup = true;
aggTestColl.Query.Load();

Yields
==============
SELECT [IsActive],[DepartmentID] ,COUNT(*) AS 'Count' FROM [AggregateTest]
WHERE ([IsActive] = @IsActive1 )
GROUP BY [IsActive],[DepartmentID] WITH ROLLUP
ORDER BY [DepartmentID] ASC,[IsActive] ASC

Same binary code runs on all databases.

re: Oops, we did it again

mattwar — Fri, 12 May 2006 18:52:20 GMT

Mike, you could certainly add LINQ to your product. It would be relatively simple to translate IQueryable<T> expression trees into your query API, so it would simply bolt on top of what you have now.

By implementing IQueryable<AggregateTest> on your AggregateTestCollection class your users could write LINQ queries.

New LINQ CTP, Awesome New Features

hacked.brain — Fri, 12 May 2006 19:36:41 GMT

re: Oops, we did it again

Mike Griffin — Fri, 12 May 2006 19:45:01 GMT

That's exactly what we were thinking. We provide a whole other superset of functionality but thought exactly as you suggested, implement the IQueryable<> syntax. We're releasing 1.4 this weekend which adds MySQL and some other cools stuff. Then 1.5 adds full hierarchical support. Of course we generate it all from your db schema. What's cool is that our NUnit test suite runs the exact same binary code against Oracle, Access, Microosft SQL, and MySQL the only difference being a connection string (of course, you have to use a schema that works in all databases but it's very forgiving). Anyway, we're thinking along the same lines ...

Вышел майский CTP LINQ Project

Alex N. Winokuroff — Sat, 13 May 2006 10:41:18 GMT

Добавлены новые возможности: Поддержка запросов времени выполнения, соединений т

Meet IQueryable<T>

RightHand blogs — Sat, 13 May 2006 13:10:15 GMT

One of the biggest Linq improvements from the last CTP is IQueryable&lt;T&gt; which allows polymorphic...

LINQ non è (solo) un O/R mapper

Marco Russo — Mon, 15 May 2006 11:25:00 GMT

Qualche mese fa scrivevo qualche commento relativamente al ruolo di LINQ. Il recente rilascio di una...

On the C# 3.0 Preview: Some Thoughts on LINQ

Dare Obasanjo aka Carnage4Life — Wed, 17 May 2006 16:36:22 GMT

Tales from a Trading Desk » Blog Archive » LINQ - May CTP

Tales from a Trading Desk » Blog Archive » LINQ - May CTP — Wed, 17 May 2006 23:41:21 GMT

PingBack from http://mdavey.wordpress.com/2006/05/11/linq-may-ctp/

LINQ starting to take shape

Simon Thorneycroft and Jonathan Hodgson — Sun, 21 May 2006 21:41:33 GMT

After false steps of ObjectSpaces and non-existent O/R mapping tools from Microsoft, the LINQ family...

LINQ starting to take shape

Simon Thorneycroft and Jonathan Hodgson — Sun, 21 May 2006 21:45:40 GMT

After false steps of ObjectSpaces and non-existent O/R mapping tools from Microsoft, the LINQ family...

re: Oops, we did it again

Christopher Shain — Mon, 22 May 2006 16:49:07 GMT

I do a good amount of work in the multidimentional (MDX) query space. Will LINQ be extended for that paradigm also?

Crazy about G-LINQ

Gaspar Nagy — Wed, 31 May 2006 20:08:43 GMT

PingBack from <a href="http://blog.genom-e.com/default,date,2006-05-31.aspx">http://blog.genom-e.com/default,date,2006-05-31.aspx</a>

re: Oops, we did it again

gay rape — Sat, 03 Jun 2006 00:51:51 GMT

We are wellocme to it's configuration.

re: Oops, we did it again

Roger Johansson — Mon, 05 Jun 2006 13:56:46 GMT

This is soo cool.
We are currently implementing Linq support for our opensource mapper (NPersist)

http://blogs.wdevs.com/phirephly/archive/2006/06/05/13420.aspx#13422

it works lovely..
kudos to the Linq team :-)

ADO.NET vNext Entity Framework documents are back

Erwyn van der Meer — Sun, 18 Jun 2006 00:33:37 GMT

The documents on ADO.NET vNext that were previously pulled from MSDN have been republished by Microsoft.I...

re: LINQ: GetQueryText

Dan Miser — Fri, 23 Jun 2006 20:34:14 GMT

LINQ for Beginners Part I

Charlie Calvert's Community Blog — Mon, 30 Oct 2006 20:14:47 GMT

This is the first in a series of posts on C# and LINQ. These posts will describe a natural, easy to understand

The LINQ Effect: Unifying and Extending Data Access

Mint Source :: The Blog — Thu, 23 Nov 2006 12:12:27 GMT

By Matt Duffin. So, you’re creating an application… no surprise there. As part of that application, you

re: Oops, we did it again

rod — Wed, 04 Apr 2007 11:31:08 GMT

following the example, i get the error ->

The type or method has 2 generic parameter(s), but 1 generic argument(s) were provided. A generic argument must be provided for each generic parameter

from the call -> q.CreateQuery(where);

Im Trying to build a runtime hack to get around the fact linq doesnt support array.contains by building my where clause manually.

Oops, we did it again

re: Oops, we did it again

re: Oops, we did it again

re: Oops, we did it again

re: Oops, we did it again

Linq May CTP released - and info on Query Trees and IQueryable

Linq May CTP released - and info on Query Trees and IQueryable

LINQ May CTP

re: Oops, we did it again

re: Oops, we did it again

New LINQ CTP, Awesome New Features

LINQ CTP May 2006

Why wait when you can have it now?

For Discusssion?

re: Oops, we did it again

New LINQ CTP, Awesome New Features

re: Oops, we did it again

Вышел майский CTP LINQ Project

Meet IQueryable&lt;T&gt;

LINQ non &#232; (solo) un O/R mapper

On the C# 3.0 Preview: Some Thoughts on LINQ

Tales from a Trading Desk » Blog Archive » LINQ - May CTP

LINQ starting to take shape

LINQ starting to take shape

re: Oops, we did it again

Crazy about G-LINQ

re: Oops, we did it again

re: Oops, we did it again

ADO.NET vNext Entity Framework documents are back

re: LINQ: GetQueryText

LINQ for Beginners Part I

The LINQ Effect: Unifying and Extending Data Access

re: Oops, we did it again

Meet IQueryable<T>

LINQ non è (solo) un O/R mapper