Improvement, since Alin claims that he has discussed this with you previously.
Cheers Niclas On Tue, May 6, 2008 at 8:37 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > > Niclas Hedhman wrote: > > On Tue, May 6, 2008 at 7:03 PM, Peter Neubauer <[EMAIL PROTECTED]> wrote: > > > >> an example on how to store and retrieve deep composite and entity > >> graphs would be good. > > > > This is not about storage and retrieval. It is about query, and funny > > enough not really a related topic. > > > > Storage and retrieval is straight forward, access the fields as you > > normally would, and the entity stores handles the loading for you. > > What we are looking at here is whether nested properties > > can/should/must be indexed and therefor queryable. > > Since we are indexing all properties and relations from entities I can't > see any reason off the top of my head why this shouldn't just work > straight away. Seems more like a bug in the current implementation than > an improvement. > > The only thing I can see being tricky is if you want to do casting > through the traversal. Example: > Entity Employee -> Entity Employer (Company) -> HasOwner (other > interface on Company) -> Property Name = "Rickard" > i.e. find all Employees working for a Company having an owner named > Rickard. Employee will have an Association to Employer, but that must > then be cast to HasOwner in order to access the Owner, and then cast to > something where the Name can be specified. How to do these casts during > the Query construction is non-trivial since there's nothing in the > interfaces that suggests whether this is possible or not (and there > probably shouldn't be). Any ideas on how to solve this? > > /Rickard > > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
