Re: WO vs. .Net 3.5 LINQ

On Dec 1, 2007, at 12:53 PM, Kieran Kelleher wrote:
>
> At the end of the day, the objective of EOF was to abstract object  
> selection in a natural object oriented way and those qualifiers can  
> filter in memory object graph or using a database adaptor can  
> generate SQL for the one of many databases the developer may use.

There is also the very important EOF concept of a local editing  
sandbox (EOEditingContext) that gets synchronized with the other  
sandboxes after a successful save operation.

Chuck

> On Dec 1, 2007, at 2:37 PM, Helge Hess wrote:
>
>> On 27.11.2007, at 03:11, 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?
>>
>> As far as I can see LINQ is similiar to the EOQualifier /  
>> EOFetchSpecification classes in EOF (plus EOQualifierEvaluation).
>> With the difference that you can write it inline in your source  
>> code. In EOF you usually put those into the model.
>>
>> Greets,
>>   Helge
>> _______________________________________________
>> WebObjects-talk mailing list
>> [email protected]
>> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>
> _______________________________________________
> WebObjects-talk mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-talk
>

-- 

Practical WebObjects - for developers who want to increase their  
overall knowledge of WebObjects or who are trying to solve specific  
problems.
http://www.global-village.net/products/practical_webobjects