From: Rafael Kitover Date: Thu, 24 Dec 2009 15:13:03 +0000 (+0000) Subject: pod fixes for UpgradingFromV4 X-Git-Tag: 0.04999_13~23^2 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=61b3350655e40b9f9f7ef3066ce4ce76dcb75107;p=dbsrgits%2FDBIx-Class-Schema-Loader.git pod fixes for UpgradingFromV4 --- diff --git a/lib/DBIx/Class/Schema/Loader/Base.pm b/lib/DBIx/Class/Schema/Loader/Base.pm index 889e429..ea22c4f 100644 --- a/lib/DBIx/Class/Schema/Loader/Base.pm +++ b/lib/DBIx/Class/Schema/Loader/Base.pm @@ -50,7 +50,7 @@ __PACKAGE__->mk_ro_accessors(qw/ monikers dynamic naming - _upgrading + _upgrading_from /); __PACKAGE__->mk_accessors(qw/ diff --git a/lib/DBIx/Class/Schema/Loader/Manual/UpgradingFromV4.pod b/lib/DBIx/Class/Schema/Loader/Manual/UpgradingFromV4.pod index c5869aa..d64f056 100644 --- a/lib/DBIx/Class/Schema/Loader/Manual/UpgradingFromV4.pod +++ b/lib/DBIx/Class/Schema/Loader/Manual/UpgradingFromV4.pod @@ -26,7 +26,7 @@ relationship accessor itself. It will also more correctly infer the relationship type, e.g. some relationships that were previously detected as a C will now be a C -(when the foreign key refers to a unique index.) +(when it detects a unique constraint on the foreign key column.) =item * @@ -55,14 +55,14 @@ To control this behavior see L. =head2 Static Schemas When reading a C from a static schema generated with an C<0.04> -version of Loader, backward compatibility mode willl be turned on, unless -overridden with the naming accessor. +version of Loader, backward compatibility mode will default to on, unless +overridden with the C attribute. =head2 Dynamic Schemas Dynamic schemas will always by default use C<0.04006> mode. -To upgrade a dynamic schema, set the naming accessor (which is proxied to the +To upgrade a dynamic schema, set the naming attribute (which is proxied to the loader) in your C: __PACKAGE__->naming('current');