| (no subject) [message #687358] |
Thu, 02 June 2011 06:44 |
 saurav sarkar
Messages: 428
Registered: July 2009 |
Senior Member |
|
|
Quote:
> The first construct (mean: everything in index.executeQueryCommand(...)) is only to get ALL indexed resources, right? First i thought this way is every time necessary.
>
> c) Ok, i get URIs and when i need/want the EObjects i have to loaded with the URIs. That is what you mean, i think, or?
Yes the first construct is to get all the resource indexed.You may chose to give some other URIs.
Then yes once you get the URIs you can load the resources or if you use attributes in your queries the resources are already
loaded and the attributes in the result are shown to you.
Quote:
> I split the handling of things around Query 2 in two classes:
> - IndexQuery2Manager
> - QueryCommandsManager
>
> Make things a bit more clear for me and it make fun to work with Query 2. Now i have to take a closer look to the SQL like language.
Its good to hear that you are liking to use Query2.You may wish to contribute your APIs back to Query2 if you feel it will help the community.
And yes go ahead with trying the SQL like language.Its pretty nice feature we have.
Would be awaiting for your comments/suggestions on that.
cheers,
Saurav
--
My Blog http://codifyit.blogspot.com/
Follow me: http://twitter.com/sauravs
My Blog http://codifyit.blogspot.com/
Follow me: http://twitter.com/sauravs
|
|
|
Powered by
FUDForum. Page generated in 0.06280 seconds
] 
Search
Help
Register
Login
Home
