Merge branch 'current/for_cpan_index' into current/dq

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Manual / Troubleshooting.pod

diff --git a/lib/DBIx/Class/Manual/Troubleshooting.pod b/lib/DBIx/Class/Manual/Troubleshooting.pod
index 6ca0dd3..b28a960 100644 (file)
--- a/lib/DBIx/Class/Manual/Troubleshooting.pod
+++ b/lib/DBIx/Class/Manual/Troubleshooting.pod
@@ -21,7 +21,7 @@ Alternatively use the C<< storage->debug >> class method:-
 
 To send the output somewhere else set debugfh:-
 
-  $schema->storage->debugfh(IO::File->new('/tmp/trace.out', 'w');
+  $schema->storage->debugfh(IO::File->new('/tmp/trace.out', 'w'));
 
 Alternatively you can do this with the environment variable, too:-
 
@@ -96,7 +96,7 @@ up with the following errors:
 2) syntax error at or near "user" - due to "user" in the JOIN clause
 
 The solution is to enable quoting - see
-L<DBIx::Class::Manual::Cookbook/Setting_quoting_for_the_generated_SQL> for
+L<DBIx::Class::Manual::Cookbook/Setting quoting for the generated SQL> for
 details.
 
 =head2 column "foo DESC" does not exist ...
@@ -112,7 +112,7 @@ should be written as:
   $rs->search( {}, { order_by => { -desc => 'name' } } );
 
 For more ways to express order clauses refer to
-L<SQL::Abstract/ORDER_BY_CLAUSES>
+L<SQL::Abstract/ORDER BY CLAUSES>
 
 =head2 Perl Performance Issues on Red Hat Systems
 
@@ -134,7 +134,7 @@ with full current updates will not be subject to this problem):-
 
 This issue is due to perl doing an exhaustive search of blessed objects
 under certain circumstances.  The problem shows up as performance
-degradation exponential to the number of L<DBIx::Class> row objects in
+degradation exponential to the number of L<DBIx::Class> result objects in
 memory, so can be unnoticeable with certain data sets, but with huge
 performance impacts on other datasets.
 
@@ -152,7 +152,7 @@ L<http://rhn.redhat.com/errata/RHBA-2008-0876.html>
 It has been observed, using L<DBD::ODBC>, that creating a L<DBIx::Class::Row>
 object which includes a column of data type TEXT/BLOB/etc. will allocate
 LongReadLen bytes.  This allocation does not leak, but if LongReadLen
-is large in size, and many such row objects are created, e.g. as the
+is large in size, and many such result objects are created, e.g. as the
 output of a ResultSet query, the memory footprint of the Perl interpreter
 can grow very large.