|Subject:||Doc-Patch for ::Row->delete|
i missunderstand the behavior from the ->delete. Simple a liddle more text to explain how it works.
--- lib/DBIx/Class/Row.pm.orig 2009-12-11 16:53:21.000000000 +0100 +++ lib/DBIx/Class/Row.pm 2009-12-11 16:54:12.000000000 +0100 @@ -527,7 +527,8 @@ this behaviour off, pass C<< cascade_delete => 0 >> in the C<$attr> hashref of the relationship, see L<DBIx::Class::Relationship>. Any database-level cascade or restrict will take precedence over a -DBIx-Class-based cascading delete. +DBIx-Class-based cascading delete. The DBIx-Class-bases delete will first +delete the current object and then select and delete the related rows. If you delete an object within a txn_do() (see L<DBIx::Class::Storage/txn_do>) and the transaction subsequently fails, the row object will remain marked as