I've read this paragraph (http://docs.sqlalchemy.org/en/latest/orm/session.html#unitofwork-cascades) many many times and still can't think of a practical example of what is being discussed.
save-update cascade also cascades the *pending history* of the target > attribute, meaning that objects which were removed from a scalar or > collection attribute whose changes have not yet been flushed are also > placed into the target session. This is because they may have foreign key > attributes present which will need to be updated to no longer refer to the > parent. I don't think my English is the main stumbling block here because I understand the meaning of each word, but as soon as I'm putting them together I'm completely lost. Could someone give a simple example here to illustrate the main point in this paragraph please? Highly appreciated. Thanks. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
