From: Oliver Gorwits <oliver@cpan.org>
Date: Mon, 10 May 2010 12:17:11 +0000 (+0000)
Subject: minor change to POD, added limitation for CASCADE
X-Git-Tag: v0.900201~11
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d57ee845eaf1259197775dcae2206c184c637f7c;p=dbsrgits%2FDBIx-Class-Journal.git

minor change to POD, added limitation for CASCADE
---

diff --git a/lib/DBIx/Class/Journal.pm b/lib/DBIx/Class/Journal.pm
index 54e0b9d..465c649 100644
--- a/lib/DBIx/Class/Journal.pm
+++ b/lib/DBIx/Class/Journal.pm
@@ -86,13 +86,13 @@ Load the module into your L<DBIx::Class> Schema Class:
 
  __PACKAGE__->load_components(qw/Schema::Journal/);
 
-And then call C<< $schema->bootstrap_journal >> (I<once only>) to create all
-the tables necessary for the journal, in your database.
-
 Optionally set where the journal is stored:
 
  __PACKAGE__->journal_connection(['dbi:SQLite:t/var/Audit.db']);
 
+And then call C<< $schema->bootstrap_journal >> (I<once only>) to create all
+the tables necessary for the journal, in your database.
+
 Later on, in your application, wrap operations in transactions, and optionally
 associate a user with the changeset:
 
@@ -337,6 +337,11 @@ Only single-column integer primary key'd tables are supported for auditing.
 
 =item *
 
+Rows changed as a result of C<CASCADE> settings on your database will not be
+detected by the module and hence not journalled.
+
+=item *
+
 Updates made via L<DBIx::Class::ResultSet/update> are not yet supported.
 
 =item *