From: Nigel Metheringham Date: Fri, 7 May 2010 13:54:36 +0000 (+0000) Subject: Clarification to cascade_update attribute documentation X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=cee0c9b187a09934aa46cafb2d1cc78a1b6e9eae;p=dbsrgits%2FDBIx-Class-Historic.git Clarification to cascade_update attribute documentation --- diff --git a/lib/DBIx/Class/Relationship/Base.pm b/lib/DBIx/Class/Relationship/Base.pm index 2f8083a..b4984e7 100644 --- a/lib/DBIx/Class/Relationship/Base.pm +++ b/lib/DBIx/Class/Relationship/Base.pm @@ -148,10 +148,10 @@ C relationships. You can disable this behaviour on a per-relationship basis by supplying C<< cascade_update => 0 >> in the relationship attributes. -The cascaded operations are performed after the requested update, -so if your database has a constraint on the relationship, it will -have updated/updated the related records or raised an exception -before DBIx::Class gets to perform the cascaded operation. +This is not a RDMS style cascade update - it purely means that when +an object has update called on it, all the related objects also +have update called. It will not change foreign keys automatically - +you must arrange to do this yourself. =item on_delete / on_update