Author: hmbrand
Date: Mon Jun 7 12:52:19 2010
New Revision: 14120
Modified:
dbi/trunk/DBI.pm
dbi/trunk/lib/DBD/DBM.pm
dbi/trunk/lib/DBD/File.pm
dbi/trunk/lib/DBD/Gofer/Transport/Base.pm
dbi/trunk/lib/DBD/Multiplex.pm
dbi/trunk/lib/DBD/Proxy.pm
dbi/trunk/lib/DBI/DBD.pm
dbi/trunk/lib/DBI/Gofer/Execute.pm
dbi/trunk/lib/DBI/Profile.pm
dbi/trunk/lib/DBI/ProfileDumper/Apache.pm
dbi/trunk/lib/DBI/ProxyServer.pm
dbi/trunk/lib/DBI/PurePerl.pm
dbi/trunk/lib/DBI/SQL/Nano.pm
dbi/trunk/lib/Win32/DBIODBC.pm
Log:
Spell checking fixes
Modified: dbi/trunk/DBI.pm
==============================================================================
--- dbi/trunk/DBI.pm (original)
+++ dbi/trunk/DBI.pm Mon Jun 7 12:52:19 2010
@@ -1101,7 +1101,7 @@
sub data_string_diff {
# Compares 'logical' characters, not bytes, so a latin1 string and an
- # an equivalent unicode string will compare as equal even though their
+ # an equivalent Unicode string will compare as equal even though their
# byte encodings are different.
my ($a, $b) = @_;
unless (defined $a and defined $b) { # one undef
@@ -2267,7 +2267,7 @@
data to and from the driver without change. It is up to the driver
implementors to decide how they wish to handle such binary data.
-Perl supports two kinds of strings: unicode (utf8 internally) and non-unicode
+Perl supports two kinds of strings: Unicode (utf8 internally) and non-Unicode
(defaults to iso-8859-1 if forced to assume an encoding). Drivers should
accept both kinds of strings and, if required, convert them to the character
set of the database being used. Similarly, when fetching from the database
@@ -6818,7 +6818,7 @@
It is possible that the values in the hash returned by C<ParamTypes>
are not exactly the same as those passed to bind_param() or execute().
-Param attributes specified using the abreviated form, like this:
+Param attributes specified using the abbreviated form, like this:
$sth->bind_param(1, SQL_INTEGER);
@@ -7210,7 +7210,7 @@
if ( $@ eq "TIMEOUT\n" ) { ... }
elsif ($@) { ... } # some other error
-The first (outer) eval is used to avoid the unlikey but possible
+The first (outer) eval is used to avoid the unlikely but possible
chance that the "code to execute" dies and the alarm fires before it
is cancelled. Without the outer eval, if this happened your program
will die if you have no ALRM handler or a non-local alarm handler
Modified: dbi/trunk/lib/DBD/DBM.pm
==============================================================================
--- dbi/trunk/lib/DBD/DBM.pm (original)
+++ dbi/trunk/lib/DBD/DBM.pm Mon Jun 7 12:52:19 2010
@@ -1030,7 +1030,7 @@
"user_name='Fred Bloggs' - so the search will find it very quickly without
having to loop through however many names were inserted into the table.
-In contrast, thes searches on the same table are not optimized:
+In contrast, these searches on the same table are not optimized:
1. SELECT phone FROM user WHERE user_name < 'Fred';
2. SELECT user_name FROM user WHERE phone = '233-7777';
Modified: dbi/trunk/lib/DBD/File.pm
==============================================================================
--- dbi/trunk/lib/DBD/File.pm (original)
+++ dbi/trunk/lib/DBD/File.pm Mon Jun 7 12:52:19 2010
@@ -1423,7 +1423,7 @@
=back
For DBD::CSV tables this means, once opened 'foo.csv' as table named 'foo',
-another table named 'foo' accessing the file 'foo.csl' cannot be opened.
+another table named 'foo' accessing the file 'foo.txt' cannot be opened.
Accessing 'foo' will always access the file 'foo.csv' in memorized
C<f_dir>, locking C<f_lockfile> via memorized C<f_lock>.
Modified: dbi/trunk/lib/DBD/Gofer/Transport/Base.pm
==============================================================================
--- dbi/trunk/lib/DBD/Gofer/Transport/Base.pm (original)
+++ dbi/trunk/lib/DBD/Gofer/Transport/Base.pm Mon Jun 7 12:52:19 2010
@@ -358,7 +358,7 @@
=head1 TRACING
-Tracing of gofer requests and reponses can be enabled by setting the
+Tracing of gofer requests and responses can be enabled by setting the
C<DBD_GOFER_TRACE> environment variable. A value of 1 gives a reasonably
compact summary of each request and response. A value of 2 or more gives a
detailed, and voluminous, dump.
Modified: dbi/trunk/lib/DBD/Multiplex.pm
==============================================================================
--- dbi/trunk/lib/DBD/Multiplex.pm (original)
+++ dbi/trunk/lib/DBD/Multiplex.pm Mon Jun 7 12:52:19 2010
@@ -1018,7 +1018,7 @@
method. That's one symptom of the next item:
Attributes may not behave as expected because the DBI intercepts
-atribute FETCH calls and returns the value, if there is one, from
+attribute FETCH calls and returns the value, if there is one, from
DBD::Multiplex's attribute cache and doesn't give DBD::Multiplex a
change to multiplex the FETCH. That's fixed from DBI 1.36.
Modified: dbi/trunk/lib/DBD/Proxy.pm
==============================================================================
--- dbi/trunk/lib/DBD/Proxy.pm (original)
+++ dbi/trunk/lib/DBD/Proxy.pm Mon Jun 7 12:52:19 2010
@@ -879,7 +879,7 @@
This attribute can be used to reduce network traffic: If the
application is calling $sth->finish() then the proxy tells the server
to finish the remote statement handle. Of course this slows down things
-quite a lot, but is prefectly good for reducing memory usage with
+quite a lot, but is perfectly good for reducing memory usage with
persistent connections.
However, if you set the I<proxy_no_finish> attribute to a TRUE value,
@@ -960,7 +960,7 @@
$tables->{"passwd"} = { "sep_char" => ":", "eol" => "\n";
While the examples work fine without the proxy, the fail due to a
-subtile difference in step 1: By DBI magic, the hash ref
+subtle difference in step 1: By DBI magic, the hash ref
$dbh->{'csv_tables'} is returned from the server to the client.
The client creates a local copy. This local copy is the result of
step 1. In other words, step 2 modifies a local copy of the hash ref,
Modified: dbi/trunk/lib/DBI/DBD.pm
==============================================================================
--- dbi/trunk/lib/DBI/DBD.pm (original)
+++ dbi/trunk/lib/DBI/DBD.pm Mon Jun 7 12:52:19 2010
@@ -1816,7 +1816,7 @@
Since B<DBI> post v1.607, if a C<dbd_db_login6_sv()> macro is defined (for
a function like dbd_db_login6 but with scalar pointers for the dbname,
username and password), it will be used instead. This will allow your
-login6 function to see if there are any unicode characters in the
+login6 function to see if there are any Unicode characters in the
dbname.
People used to just pick Oracle's F<dbdimp.c> and use the same names,
@@ -2904,7 +2904,7 @@
duration of the call: the trace flags of the handle are OR'd into the
trace flags of the DBI, and if the handle has a higher trace level
then the DBI trace level is raised to match it. The previous DBI trace
-setings are restored when the called method returns.
+settings are restored when the called method returns.
=head2 Trace Level
Modified: dbi/trunk/lib/DBI/Gofer/Execute.pm
==============================================================================
--- dbi/trunk/lib/DBI/Gofer/Execute.pm (original)
+++ dbi/trunk/lib/DBI/Gofer/Execute.pm Mon Jun 7 12:52:19 2010
@@ -852,7 +852,7 @@
=item err=N
-Sets the current failure err vaue to N (instead of the DBI's default 'standard
+Sets the current failure err value to N (instead of the DBI's default 'standard
err value' of 2000000000). This is useful when you want to simulate a
specific error.
Modified: dbi/trunk/lib/DBI/Profile.pm
==============================================================================
--- dbi/trunk/lib/DBI/Profile.pm (original)
+++ dbi/trunk/lib/DBI/Profile.pm Mon Jun 7 12:52:19 2010
@@ -71,7 +71,7 @@
The profile data is accumulated as 'leaves on a tree'. The 'path' through the
branches of the tree to a particular leaf is determined dynamically for each
sample.
-This is a key feature of DBI profiliing.
+This is a key feature of DBI profiling.
For each profiled method call the DBI walks along the Path and uses each value
in the Path to step into and grow the Data tree.
@@ -189,7 +189,7 @@
negative number will reverse the path. Thus "-6" will group by method name then
statement.
-The spliting and parsing of string values assigned to the Profile
+The splitting and parsing of string values assigned to the Profile
attribute may seem a little odd, but there's a good reason for it.
Remember that attributes can be embedded in the Data Source Name
string which can be passed in to a script as a parameter. For
@@ -368,9 +368,9 @@
Which shows the total time spent inside the DBI, with a count of
the total number of method calls and the name of the script being
-run, then a formated version of the profile data tree.
+run, then a formatted version of the profile data tree.
-If the results are being formated when the perl process is exiting
+If the results are being formatted when the perl process is exiting
(which is usually the case when the DBI_PROFILE environment variable
is used) then the percentage of time the process spent inside the
DBI is also shown. If the process is not exiting then the percentage is
@@ -491,13 +491,13 @@
);
Returns the collected data ($dbh->{Profile}{Data}) reformatted into a list of
formatted strings.
-In scalar context the list is returned as a single contatenated string.
+In scalar context the list is returned as a single concatenated string.
A hashref can be used to pass in arguments, the default values are shown in
the example above.
The C<node> and <path> arguments are passed to as_node_path_list().
-The C<separator> argument is used to join the elemets of the path for each
leaf node.
+The C<separator> argument is used to join the elements of the path for each
leaf node.
The C<sortsub> argument is used to pass in a ref to a sub that will order the
list.
The subroutine will be passed a reference to the array returned by
Modified: dbi/trunk/lib/DBI/ProfileDumper/Apache.pm
==============================================================================
--- dbi/trunk/lib/DBI/ProfileDumper/Apache.pm (original)
+++ dbi/trunk/lib/DBI/ProfileDumper/Apache.pm Mon Jun 7 12:52:19 2010
@@ -61,7 +61,7 @@
and using chronolog to write to the logs directory, then you'll need to change
the default.
-You can change the destination directory either by secifying a C<Dir> value
+You can change the destination directory either by specifying a C<Dir> value
when creating the profile (like C<File> in the L<DBI::ProfileDumper> docs),
or you can use the C<DBI_PROFILE_APACHE_LOG_DIR> env var to change that. For
example:
Modified: dbi/trunk/lib/DBI/ProxyServer.pm
==============================================================================
--- dbi/trunk/lib/DBI/ProxyServer.pm (original)
+++ dbi/trunk/lib/DBI/ProxyServer.pm Mon Jun 7 12:52:19 2010
@@ -526,7 +526,7 @@
=item I<version> (B<--version>)
-Supresses startup of the server; instead the version string will
+Suppresses startup of the server; instead the version string will
be printed and the program exits immediately.
=back
@@ -545,7 +545,7 @@
with some additional attributes in the client list.
The config file is a Perl script. At the top of the file you may include
-arbitraty Perl source, for example load drivers at the start (useful
+arbitrary Perl source, for example load drivers at the start (useful
to enhance performance), prepare a chroot environment and so on.
The important thing is that you finally return a hash ref of option
Modified: dbi/trunk/lib/DBI/PurePerl.pm
==============================================================================
--- dbi/trunk/lib/DBI/PurePerl.pm (original)
+++ dbi/trunk/lib/DBI/PurePerl.pm Mon Jun 7 12:52:19 2010
@@ -1113,7 +1113,7 @@
=head1 USAGE
The usage is the same as for standard DBI with the exception
-that you need to set the enviornment variable DBI_PUREPERL if
+that you need to set the environment variable DBI_PUREPERL if
you want to use the PurePerl version.
DBI_PUREPERL == 0 (the default) Always use compiled DBI, die
@@ -1178,7 +1178,7 @@
=head2 Tracing
Trace functionality is more limited and the code to handle tracing is
-only embeded into DBI:PurePerl if the DBI_TRACE environment variable
+only embedded into DBI:PurePerl if the DBI_TRACE environment variable
is defined. To enable total tracing you can set the DBI_TRACE
environment variable as usual. But to enable individual handle
tracing using the trace() method you also need to set the DBI_TRACE
Modified: dbi/trunk/lib/DBI/SQL/Nano.pm
==============================================================================
--- dbi/trunk/lib/DBI/SQL/Nano.pm (original)
+++ dbi/trunk/lib/DBI/SQL/Nano.pm Mon Jun 7 12:52:19 2010
@@ -950,7 +950,7 @@
Tim Bunce provided the original idea for this module, helped me out of the
tangled trap of namespace, and provided help and advice all along the way.
Although I wrote it from the ground up, it is based on Jochen Weidmann's
-orignal design of SQL::Statement, so much of the credit for the API goes
+original design of SQL::Statement, so much of the credit for the API goes
to him.
=head1 AUTHOR AND COPYRIGHT
Modified: dbi/trunk/lib/Win32/DBIODBC.pm
==============================================================================
--- dbi/trunk/lib/Win32/DBIODBC.pm (original)
+++ dbi/trunk/lib/Win32/DBIODBC.pm Mon Jun 7 12:52:19 2010
@@ -239,7 +239,7 @@
=head1 TO DO
-Error handling is virtually non-existant.
+Error handling is virtually non-existent.
=head1 AUTHOR
