I have a one-to-many object relation, A-to-B.
When an instance of A with several Bs is created it needs to be
persisted by SQLAlchemy. I have that via save-update rule. But when I
delete an A I DON'T WANT SQLAlchemy to do anything to its Bs - it's
taken care of by foreign key constraints in the DB. Instead it deletes
them explicitly if there's a delete cascade rule or tries to nullify
Bs' FK fields for any other cascade rule combination.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
