From: David Schmidt Date: Mon, 30 Dec 2013 09:32:32 +0000 (+0100) Subject: Fixed typos X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a9697bd06f21230c6c98cbade589374103d16a0e;p=dbsrgits%2FDBIx-Class-Historic.git Fixed typos --- diff --git a/.mailmap b/.mailmap index 210ba67..f9e091e 100644 --- a/.mailmap +++ b/.mailmap @@ -13,8 +13,9 @@ Brendan Byrd Brendan Byrd Brian Phillips David Kamholz -David Schmidt -David Schmidt +David Schmidt +David Schmidt +David Schmidt Devin Austin Felix Antonius Wilhelm Ostmann Gerda Shank diff --git a/lib/DBIx/Class/Manual/Cookbook.pod b/lib/DBIx/Class/Manual/Cookbook.pod index 36b891e..0cb560b 100644 --- a/lib/DBIx/Class/Manual/Cookbook.pod +++ b/lib/DBIx/Class/Manual/Cookbook.pod @@ -1183,7 +1183,7 @@ of your application to support a change lifecycle (e.g. DEV, TEST, PROD) and the DB schemas are named based on the environment (e.g. database1_dev). However, one can dynamically "map" to the proper DB schema by overriding the -L method in your Schema class and +L method in your Schema class and building a renaming facility, like so: package MyApp::Schema; @@ -1223,13 +1223,13 @@ building a renaming facility, like so: 1; -By overriding the L +By overriding the L method and extracting a custom option from the provided \%attr hashref one can then simply iterate over all the Schema's ResultSources, renaming them as needed. To use this facility, simply add or modify the \%attr hashref that is passed to -L, as follows: +L, as follows: my $schema = MyApp::Schema->connect(