Hello, first of all, thnak you for your fast answer. I was refering to : > > A database level ON DELETE cascade is configured effectively on the > *many-to-one* side of the relationship; that is, we configure it relative > to the FOREIGN KEY constraint that is the “many” side of a relationship. > At the ORM level, *this direction is reversed*. SQLAlchemy handles the > deletion of “child” objects relative to a “parent” from the “parent” side, > which means that delete and delete-orphan cascade are configured on the > *one-to-many* side
Marc V. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/8a5b9f82-e20a-4bb7-a7cc-eeb6c87d6719%40googlegroups.com.
