Hi Michael, Thanks for your answer.
Currently, using the REST mode, I wrote all my queries (at Read side) using pure Cypher (without SDN at all). However, I'm still using SDN to query some data that my Command strictly needs, like retrieving entities (Indeed, I separated read and commands (CQ(R)S) in my application). I think the best way would be to write cypher queries for some complex parts of the commands too. (like an Entity having 4 collections annotated with @Fetch). Even if it would break Entity data encapsulation, like I evoked above... Writing an unmanaged extension would be hard to manage IMHO, since it would split the application into more parts. Thanks a lot :) Michael On Tuesday, July 15, 2014 2:05:58 AM UTC+2, Michael Hunger wrote: > > Hi Michael, > > I've had plans for a long time to write a different implementation of SDN > that is runs on top of a Cypher based OGM which then uses a Cypher > connector (like the Neo4j-JDBC driver) to talk t an embedded or remote > Neo4j database. > > Unfortunately I haven't yet found the time to address that. > > Am 11.07.2014 um 01:23 schrieb Michael Azerhad <[email protected] > <javascript:>>: > > Hi, > > I well know that SDN is fully optimized for embedded database. > > > I would like to know if there are any plan (or maybe already done?) to > improve the way SDN manages @Fetch requests on lazy collections when using > REST mode. > Indeed, some use cases are very slow with it. > > Right, that's why I currently recommend to move the SDN part to the server > as an unmanaged extension. > > > A good workaround would be to write a pure Cypher query (@Query on a > repo's method) to fetch for lazy collections. > > The problem is still that the remote representation is flaky and not well > suited so you have to do multiple request to get all meta-data. > > However, this would break entity encapsulation, since I don't want to > populate the list inside the Entity => an entity is a simple POJO not aware > about repositories. > > I think the repo should probably use the query to populate a simple DTO > class (annotated with @QueryResult) which then can be used in the front-end. > > Michael > > > So it's not a pure technical question, but a curiosity :) > > Thanks a lot, > > Michael > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
