From: Aran Deltac Date: Fri, 24 Mar 2006 14:40:23 +0000 (+0000) Subject: Spleling fixes all over. X-Git-Tag: v0.06000~16 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=880a1a0cc6a48a3165656fe5daf7ec288901c3e2;hp=27f01d1f4fc106e0d27a13c6f6c9d5fa131e9447;p=dbsrgits%2FDBIx-Class.git Spleling fixes all over. --- diff --git a/lib/DBIx/Class.pm b/lib/DBIx/Class.pm index 0edcc70..a6c290d 100644 --- a/lib/DBIx/Class.pm +++ b/lib/DBIx/Class.pm @@ -101,12 +101,12 @@ Then you can use these classes in your application's code: { order_by => 'title' } ); - my $millenium_cds_rs = $ds->resultset('CD')->search( + my $millennium_cds_rs = $ds->resultset('CD')->search( { year => 2000 }, { prefetch => 'artist' } ); - my $cd = $millenium_cds_rs->next; # SELECT ... FROM cds JOIN artists ... + my $cd = $millennium_cds_rs->next; # SELECT ... FROM cds JOIN artists ... my $cd_artist_name = $cd->artist->name; # Already has the data so no query my $new_cd = $ds->resultset('CD')->new({ title => 'Spoon' }); @@ -116,7 +116,7 @@ Then you can use these classes in your application's code: $ds->txn_do(sub { $new_cd->update }); # Runs the update in a transaction - $millenium_cds_rs->update({ year => 2002 }); # Single-query bulk update + $millennium_cds_rs->update({ year => 2002 }); # Single-query bulk update =head1 DESCRIPTION diff --git a/lib/DBIx/Class/CDBICompat.pm b/lib/DBIx/Class/CDBICompat.pm index 0a45f18..dc4c8d2 100644 --- a/lib/DBIx/Class/CDBICompat.pm +++ b/lib/DBIx/Class/CDBICompat.pm @@ -39,7 +39,7 @@ __PACKAGE__->load_own_components(qw/ =head1 NAME -DBIx::Class::CDBICompat - Class::DBI Compatability layer. +DBIx::Class::CDBICompat - Class::DBI Compatibility layer. =head1 SYNOPSIS @@ -48,7 +48,7 @@ DBIx::Class::CDBICompat - Class::DBI Compatability layer. =head1 DESCRIPTION -DBIx::Class features a fully featured compability layer with L +DBIx::Class features a fully featured compatibility layer with L to ease transition for existing CDBI users. In fact, this class is just a receipe containing all the features emulated. If you like, you can choose which features to emulate by building your own class and loading it like @@ -107,7 +107,7 @@ Responsible for HasMany relationships. =item LiveObjectIndex The live object index tries to ensure there is only one version of a object -in the perl interprenter. +in the perl interpreter. =item MightHave diff --git a/lib/DBIx/Class/Manual/Component.pod b/lib/DBIx/Class/Manual/Component.pod index f74f5bf..e7c8a60 100644 --- a/lib/DBIx/Class/Manual/Component.pod +++ b/lib/DBIx/Class/Manual/Component.pod @@ -38,7 +38,7 @@ them. These components provide extra functionality beyond basic functionality that you can't live without. -L - Class::DBI Compatability layer. +L - Class::DBI Compatibility layer. L - Build forms with multiple interconnected objects. @@ -127,7 +127,7 @@ being called try printing out the Class::C3 inheritance stack. print join ', ' => Class::C3::calculateMRO('YourClass::Name'); -Check out the L docs for more information about inhertance. +Check out the L docs for more information about inheritance. =head1 SEE ALSO diff --git a/lib/DBIx/Class/Manual/Cookbook.pod b/lib/DBIx/Class/Manual/Cookbook.pod index fc3224f..5690f43 100644 --- a/lib/DBIx/Class/Manual/Cookbook.pod +++ b/lib/DBIx/Class/Manual/Cookbook.pod @@ -393,7 +393,7 @@ example of the recommended way to use it: $genus->add_to_species({ name => 'troglodyte' }); $genus->wings(2); $genus->update; - $schema->txn_do($code, $genus); # Can have a nested transation + $schema->txn_do($code, $genus); # Can have a nested transaction return $genus->species; }; @@ -542,7 +542,7 @@ instead: print $output; You could use L to search for all subclasses in the MyDB::* -namespace, which is currently left as an excercise for the reader. +namespace, which is currently left as an exercise for the reader. =head2 Schema versioning @@ -657,7 +657,7 @@ The first sets the quotesymbols. If the quote i "symmetric" as " or ' __PACKAGE__->storage->sql_maker->quote_char('"'); -is enough. If the left qoute differs form the right quote, the first +is enough. If the left quote differs form the right quote, the first notation should be used. name_sep needs to be set to allow the SQL generator to put the quotes the correct place. diff --git a/lib/DBIx/Class/Manual/Example.pod b/lib/DBIx/Class/Manual/Example.pod index e2a5166..b56f85e 100644 --- a/lib/DBIx/Class/Manual/Example.pod +++ b/lib/DBIx/Class/Manual/Example.pod @@ -4,7 +4,7 @@ DBIx::Class::Manual::Example - Simple CD database example =head1 DESCRIPTION -This tutorial will guide you through the proeccess of setting up and +This tutorial will guide you through the process of setting up and testing a very basic CD database using SQLite, with DBIx::Class::Schema as the database frontend. @@ -340,7 +340,7 @@ It should output: With these scripts we're relying on @INC looking in the current working directory. You may want to add the MyDatabase namespaces to -@INC in a different way when it comes to deployemnt. +@INC in a different way when it comes to deployment. The testdb.pl script is an excellent start for testing your database model. diff --git a/lib/DBIx/Class/Manual/Glossary.pod b/lib/DBIx/Class/Manual/Glossary.pod index 4e97234..3e9d36a 100644 --- a/lib/DBIx/Class/Manual/Glossary.pod +++ b/lib/DBIx/Class/Manual/Glossary.pod @@ -1,6 +1,6 @@ =head1 NAME -DBIx::Class::Manual::Glossary - Deconfusion of terms used +DBIx::Class::Manual::Glossary - Clarification of terms used. =head1 INTRODUCTION diff --git a/lib/DBIx/Class/Manual/Intro.pod b/lib/DBIx/Class/Manual/Intro.pod index 5483561..cad4693 100644 --- a/lib/DBIx/Class/Manual/Intro.pod +++ b/lib/DBIx/Class/Manual/Intro.pod @@ -163,7 +163,7 @@ a second database you want to access: my $other_schema = My::Schema->connect( $dsn, $user, $password, $attrs ); -Note that L does not cache connnections for you. If you +Note that L does not cache connections for you. If you use multiple connections, you need to do this manually. To execute some sql statements on every connect you can pass them to your schema after the connect: diff --git a/lib/DBIx/Class/Relationship.pm b/lib/DBIx/Class/Relationship.pm index 770953f..b308555 100644 --- a/lib/DBIx/Class/Relationship.pm +++ b/lib/DBIx/Class/Relationship.pm @@ -128,8 +128,8 @@ cascade or restrict will take precedence. =head2 might_have - My::DBIC::Schema::Author->might_have(psuedonym => 'Psuedonyms'); - my $pname = $obj->psuedonym; # to get the Psuedonym object + My::DBIC::Schema::Author->might_have(pseudonym => 'Pseudonyms'); + my $pname = $obj->pseudonym; # to get the Pseudonym object Creates an optional one-to-one relationship with a class, where the foreign class stores our primary key in one of its columns. Defaults to the primary diff --git a/lib/DBIx/Class/Relationship/Base.pm b/lib/DBIx/Class/Relationship/Base.pm index 9ea8cff..c3733e7 100644 --- a/lib/DBIx/Class/Relationship/Base.pm +++ b/lib/DBIx/Class/Relationship/Base.pm @@ -31,8 +31,8 @@ methods, for predefined ones, look in L. The condition needs to be an SQL::Abstract-style representation of the join between the tables. When resolving the condition for use in a JOIN, -keys using the psuedo-table I are resolved to mean "the Table on the -other side of the relationship", and values using the psuedo-table I +keys using the pseudo-table I are resolved to mean "the Table on the +other side of the relationship", and values using the pseudo-table I are resolved to mean "the Table this class is representing". Other restrictions, such as by value, sub-select and other tables, may also be used. Please check your database for JOIN parameter support. diff --git a/lib/DBIx/Class/ResultSet.pm b/lib/DBIx/Class/ResultSet.pm index 093a456..54d48e8 100644 --- a/lib/DBIx/Class/ResultSet.pm +++ b/lib/DBIx/Class/ResultSet.pm @@ -588,7 +588,7 @@ sub count_literal { shift->search_literal(@_)->count; } =head2 all -Returns all elements in the resultset. Called implictly if the resultset +Returns all elements in the resultset. Called implicitly if the resultset is returned in list context. =cut diff --git a/lib/DBIx/Class/Row.pm b/lib/DBIx/Class/Row.pm index 7c5cf9a..b230208 100644 --- a/lib/DBIx/Class/Row.pm +++ b/lib/DBIx/Class/Row.pm @@ -122,9 +122,9 @@ sub update { $obj->delete -Deletes the object from the database. The object is still perfectly usable -accessor-wise etc. but ->in_storage will now return 0 and the object must -be re ->insert'ed before it can be ->update'ed +Deletes the object from the database. The object is still perfectly usable, +but ->in_storage() will now return 0 and the object must re inserted using +->insert() before ->update() can be used on it. =cut diff --git a/lib/DBIx/Class/UUIDColumns.pm b/lib/DBIx/Class/UUIDColumns.pm index 76647ad..b7e4e7c 100644 --- a/lib/DBIx/Class/UUIDColumns.pm +++ b/lib/DBIx/Class/UUIDColumns.pm @@ -53,7 +53,7 @@ sub _find_uuid_module { if (eval{require Data::UUID}) { return '::Data::UUID'; } elsif ($^O ne 'openbsd' && eval{require APR::UUID}) { - # APR::UUID on openbsd causes some as yet unfound nastyness for XS + # APR::UUID on openbsd causes some as yet unfound nastiness for XS return '::APR::UUID'; } elsif (eval{require UUID}) { return '::UUID'; diff --git a/lib/DBIx/Class/UUIDMaker.pm b/lib/DBIx/Class/UUIDMaker.pm index 0baedad..f492801 100644 --- a/lib/DBIx/Class/UUIDMaker.pm +++ b/lib/DBIx/Class/UUIDMaker.pm @@ -25,7 +25,7 @@ DBIx::Class::UUIDMaker - UUID wrapper module sub as_string { my $uuid; - ...magic encantations... + ...magic incantations... return $uuid; }; diff --git a/lib/SQL/Translator/Parser/DBIx/Class.pm b/lib/SQL/Translator/Parser/DBIx/Class.pm index 53e36ef..92a6204 100644 --- a/lib/SQL/Translator/Parser/DBIx/Class.pm +++ b/lib/SQL/Translator/Parser/DBIx/Class.pm @@ -22,7 +22,7 @@ use base qw(Exporter); # ------------------------------------------------------------------- # parse($tr, $data) # -# Note that $data, in the case of this parser, is unuseful. +# Note that $data, in the case of this parser, is not useful. # We're working with DBIx::Class Schemas, not data streams. # ------------------------------------------------------------------- sub parse { @@ -80,7 +80,7 @@ sub parse { next if(!exists $rel_info->{attrs}{accessor} || $rel_info->{attrs}{accessor} eq 'multi'); # Going by the accessor type isn't such a good idea (yes, I know - # I suggested it). I think the best way to tell if something's a + # I suggested it). I think the best way to tell if something is a # foreign key constraint is to assume if it doesn't include our # primaries then it is (dumb but it'll do). Ignore any rel cond # that isn't a straight hash, but get both sets of keys in full