search

scholrly / neo4django

Drop-in Neo4j/Django integration.
GNU General Public License v3.0
357 stars 83 forks source link

Review how cascading model saves work #188

Open mhluongo opened 11 years ago

mhluongo commented 11 years ago

Right now, it appears that if you save an unsaved model A, which has been related to an unsaved model B, everything is saved properly- but if you save A, and it's related to a saved (that is, with a node) model C with unsaved property changes, those changes aren't saved.

Is this inconsistent with Django? Cascading saves definitely need performance work, so maybe kill two birds with one stone.

mhluongo commented 11 years ago

I'm pretty sure Django doesn't do cascading saves at all, by default- and to achieve something similar you'd open a transaction, and then manually save each model involved.