Re: WO vs. .Net 3.5 LINQ

 From what I know, LINQ is a SQL-like language that can be applied to  
any data collection. It's a sort of DAL. It works against XML, arrays,  
databases, etc.

So, for people familiar with SQL, and who need to do set manipulation  
against data in many (or unknown) formats, it's pretty powerful.

But it's really quite different from EOF. LINQ is good for data  
manipulation across a wide array of data sources. I'll leave it up to  
others to declare what EOF is good at. :)

John

On Monday Nov 26, 2007 10:22 PM, at 10:22 PM, Lachlan Deck wrote:

> On 27/11/2007, at 1:11 PM, Berney Bradley wrote:
>
>> I just saw that .Net 3.5 was released last week with the LINQ  
>> (Language Integrated Query) technology.  How does WO stack up when  
>> compared to the latest from MS?
>>
>> I checked the wiki and it seems there is a lack of competitive  
>> analysis between WO and other technologies.  Can anyone comment on  
>> why someone would choose WO over .Net, in light of the recent LINQ  
>> release?  I'm looking for technical reasons, not emotional or  
>> political arguments ;-)
>
> From my cursory glance at
> http://en.wikipedia.org/wiki/Language_Integrated_Query
>
> LINQ is an sql-esq language construct for .Net. So you're  
> essentially writing sql in your code such as seen on the above page.
>
> WebObject's EOF, on the other hand, abstracts sql from you (unless  
> you need it) so you're always dealing with Objects. This document  
> may help... 'Working with EOF:
> http://developer.apple.com/documentation/WebObjects/Enterprise_Objects/index.html
>
> with regards,
> --
>
> Lachlan Deck
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk