From: zby Date: Mon, 16 Feb 2009 17:25:51 +0000 (+0000) Subject: experimental X-Git-Url: https://git.dogcows.com/gitweb?p=chaz%2Fp5-DBIx-Class-ResultSet-RecursiveUpdate;a=commitdiff_plain;h=c6ce25ccefcd1b746acd71bdaea2699931cd32b6 experimental --- diff --git a/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm b/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm index dfee15b..7275d1e 100644 --- a/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm +++ b/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm @@ -270,6 +270,7 @@ Then: =head1 DESCRIPTION +This is the first release - so treat it as experimental. You can feed the ->create method with a recursive datastructure and have the related records created. Unfortunately you cannot do a similar thing with update_or_create - this module @@ -302,12 +303,13 @@ then you need to inform recursive_update about additional predicate with a secon [ 'id' ] ); +This will work with a new DBIC release. For a many_to_many (pseudo) relation you can supply a list of primary keys from the other table - and it will link the record at hand to those and only those records identified by them. This is convenient for handling web forms with check boxes (or a SELECT box with multiple choice) that let you -update such (pseudo) relations. +update such (pseudo) relations. For a description how to set up base classes for ResultSets see load_namespaces in DBIx::Class::Schema. diff --git a/t/var/dvdzbr.db b/t/var/dvdzbr.db index aed5e7e..4d090fe 100644 Binary files a/t/var/dvdzbr.db and b/t/var/dvdzbr.db differ