Hi all,

  Just a question/poll about your collective experiences when having to 
deal with cascading updates (e.g. model A includes model B, A already has a 
relationship with B, we modify B, and we save A).  I realize that SDN 
doesn't support cascading updates for reasons that Michael Hunger has 
stated that all make perfect sense.  So my question is this: When faced 
with such a situation, how have you tackled it?  I've found the easiest way 
(but not the nicest way) without reflection is writing code at the DAO 
level that goes through the appropriate embedded models of a class (i.e. 
having to hardcode such logic, which I realize is brittle/horrible) and 
checks for a "dirty" flag and then updates the object.  This seems to be 
the most direct way, though, as I said, not the most elegant.  Has anyone 
done something more sophisticated with, say, advanced mapping mode or some 
other AspectJ-based solution?  I'm curious.

  Thanks!

Cheers,
Duncan

  

-- 
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 neo4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to