Brendan Byrd <Perl@ResonatorSoft.org> <perl@resonatorsoft.org>
Brian Phillips <bphillips@cpan.org> <bphillips@digitalriver.com>
David Kamholz <dkamholz@cpan.org> <davekam@pobox.com>
-David Schmidt <davewood@gmx.at> <d.schmidt@tripwolf.com>
-David Schmidt <davewood@gmx.at> <dt@univie.ac.at>
+David Schmidt <mail@davidschmidt.at> <d.schmidt@tripwolf.com>
+David Schmidt <mail@davidschmidt.at> <dt@univie.ac.at>
+David Schmidt <mail@davidschmidt.at> <davewood@gmx.at>
Devin Austin <dhoss@cpan.org> <devin.austin@gmail.com>
Felix Antonius Wilhelm Ostmann <sadrak@cpan.org> <ostmann@sadraksaemp.intern4.websuche.de>
Gerda Shank <gshank@cpan.org> <gerda.shank@gmail.com>
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<connection|DBIx::Class::Schama/connection> method in your Schema class and
+L<connection|DBIx::Class::Schema/connection> method in your Schema class and
building a renaming facility, like so:
package MyApp::Schema;
1;
-By overriding the L<connection|DBIx::Class::Schama/connection>
+By overriding the L<connection|DBIx::Class::Schema/connection>
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<connection|DBIx::Class::Schama/connect>, as follows:
+L<connection|DBIx::Class::Schema/connect>, as follows:
my $schema
= MyApp::Schema->connect(