|
|
|
|
Re: creating filter methods in emf code. [message #1063184 is a reply to message #1063072] |
Wed, 12 June 2013 10:40  |
Eclipse User |
|
|
|
On 12-06-13 08:48, Ed Willink wrote:
> Hi
>
> If your run-time queries are known at design time you can use derived
> features.
>
Hi Ed,
Just to understand this better in the context of CDO.
Would a derived feature be able to invoke an OCL Query, which would be
handled by the OCL Query Handler, resulting in a CDOStore dip, which
would not fetch the whole collection, but filter first? In other words
can the OCL Query Handler be aware of the underlying Store and optimize
(i.e. SELECT) the queries to it?
I never managed to get a grip, if the OCL Query Handler for CDO,
supports this optimization?
What I do now is to execute a CDO SQL Query, which indeed only returns
the intended objects. Iteration is nice, but it really doesn't make
sense to fetch 10.000 objects and throw most of them away on the client
side again after 'java' filtering.
Rgds Christophe
> Regards
>
> Ed Willink
>
> On 12/06/2013 07:36, Lakhveer Singh wrote:
>> thanks,
>>
>> but isn't there any way by which we should get the sorted and filtered
>> objects from database model like by creating or modifying the methods
>> in entity class or something else?
>
|
|
|
Powered by
FUDForum. Page generated in 0.04375 seconds