> SQLAlchemy's unit of work attempts to set it to > None during the flush.
Doesn't that imply that ondelete='RESTRICT' is not honored by UoW? This leads to completely opposite behaviour between deleting via ORM (ie. session.delete) and deleting via SQL (ie. connection.execute (table.delete)). In the first case referencing columns are NULLed; in the second an error is thrown. Wouldn't it be more logical if both were the same, ie. UoW throwing IntegrityError? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
