experimental

diff --git a/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm b/lib/DBIx/Class/ResultSet/RecursiveUpdate.pm
index dfee15b22a08edd50918f2a8fb5e6776cd7abed8..7275d1ef63844d5dad79d538e19b78a525e9142c 100644 (file)
--- 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 aed5e7e03e4744eec1572054b85337b0aa9ce207..4d090fe07bdb742325bbf0ed942f47cba54591ee 100644 (file)
Binary files a/t/var/dvdzbr.db and b/t/var/dvdzbr.db differ