Skip to content

Fixed some typos. #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 3, 2013
Merged

Fixed some typos. #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions lib/DBD/mysql.pm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -920,7 +920,7 @@ method like so:
$dbh = DBI->connect("DBI:mysql:database=$db;host=$host",
$user, $password, {RaiseError => 1});

Once you have connected to a database, you can can execute SQL
Once you have connected to a database, you can execute SQL
statements with:

my $query = sprintf("INSERT INTO foo VALUES (%d, %s)",
Expand Down Expand Up @@ -1335,7 +1335,7 @@ to 0.

This attribute forces the driver to use mysql_use_result rather than
mysql_store_result. The former is faster and less memory consuming, but
tends to block other processes. mysql_store_result is the default due to that
tends to block other processes. mysql_store_result is the default due to that
fact storing the result is expected behavior with most applications.

It is possible to set the default value of the C<mysql_use_result> attribute
Expand Down Expand Up @@ -2078,7 +2078,7 @@ Tim Bunce.
The current incarnation of B<DBD::mysql> was written by Jochen Wiedmann,
then numerous changes and bug-fixes were added by Rudy Lippan. Next,
prepared statement support was added by Patrick Galbraith and
Alexy Stroganov (who also soley added embedded server
Alexy Stroganov (who also soleley added embedded server
support).

For the past seven years DBD::mysql has been maintained by
Expand Down Expand Up @@ -2117,7 +2117,7 @@ for details.

This module is maintained and supported on a mailing list, dbi-users.

To subscribe to this list, send and email to
To subscribe to this list, send and email to

dbi-users-subscribe@perl.org

Expand Down Expand Up @@ -2150,7 +2150,7 @@ Information on the DBI interface itself can be gained by typing:

Information on the DBD::mysql specifically can be gained by typing:

perldoc DBD::mysql
perldoc DBD::mysql



Expand All @@ -2162,9 +2162,9 @@ to this link:

http://rt.cpan.org

Note: until recently, MySQL/Sun/Oracle responded to bugs and assisted in
fixing bugs which many thanks should be given for their help!
This driver is outside the realm of the numerous components they support, and the
Note: until recently, MySQL/Sun/Oracle responded to bugs and assisted in
fixing bugs which many thanks should be given for their help!
This driver is outside the realm of the numerous components they support, and the
maintainer and community solely support DBD::mysql

=cut
2 changes: 1 addition & 1 deletion lib/DBD/mysql/GetInfo.pm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ sub sql_user_name {

####################
# makefunc()
# returns a ref to a sub that that calls into XS to get
# returns a ref to a sub that calls into XS to get
# values for info types that must needs be coded in C

sub makefunk ($) {
Expand Down
34 changes: 17 additions & 17 deletions lib/DBD/mysql/INSTALL.pod
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,10 +49,10 @@ http://www.activestate.com for details.
=item MySQL

You need not install the actual MySQL database server, the
client files and the devlopment files are sufficient. For
client files and the development files are sufficient. For
example, Fedora Core 4 Linux distribution comes with RPM files
(using YUM) B<mysql.i386> and B<mysql-server.i386> (use "yum search"
to find exact package names). These are sufficient, if the MySQL
(using YUM) B<mysql.i386> and B<mysql-server.i386> (use "yum search"
to find exact package names). These are sufficient, if the MySQL
server is located on a foreign machine. You may also create client
files by compiling from the MySQL source distribution and using

Expand Down Expand Up @@ -167,14 +167,14 @@ For installation from source the following RPM's are required
mysql-devel
libz-devel

Please try
Please try

yum search mysql

To see the exact names

Note: (important) FC 3 comes with MySQL 3.x, and some people have
upgraded using MySQL RPMs for newer versions. If you do this, you
upgraded using MySQL RPMs for newer versions. If you do this, you
must re-compile you DBD::mysql because your existing DBD::mysql will be
linked against the old version of MySQL's client libs. CPAN has no way to
know or detect that you have upgraded MySQL.
Expand Down Expand Up @@ -206,7 +206,7 @@ installation. This may be achieved using command line switches
which comes with most MySQL distributions. If your MySQL distribution
contains mysql_config the easiest method is to ensure this binary
is on your path.

e.g.

PATH=$PATH:/usr/local/mysql/bin
Expand Down Expand Up @@ -274,7 +274,7 @@ L</Compiler flags>. L</Linker flags>.

For Windows/CygWin there is a special section below.
L<Windows/CygWin>.


=head2 Configuration

Expand Down Expand Up @@ -373,10 +373,10 @@ If you want to configure your own settings for database name,
database user and so on, then you have to create a script with
the same name, that replies


=head2 Compiler flags

Note: the folling info about compiler and linker flags, you shouldn't have
Note: the following info about compiler and linker flags, you shouldn't have
to use these options because Makefile.PL is pretty good at utilising
mysql_config to get the flags that you need for a successful compile.

Expand Down Expand Up @@ -504,7 +504,7 @@ Below you find information on particular systems:

If you are a user of Cygwin (the Redhat distribution) you already
know, it contains a nicely running perl 5.6.1, installation of
additional modules usually works as a charme via the standard
additional modules usually works like a charm via the standard
procedure of

perl makefile.PL
Expand All @@ -523,12 +523,12 @@ You MUST compile the MySQL clients yourself under Cygwin, to get a
'libmysqlclient.a' compiled under Cygwin. Really! You'll only need
that library and the header files, you don't need any other client parts.
Continue to use the Windows binaries. And don't attempt (currently) to
build the MySQL Server part, it is unneccessary, as MySQL AB does an
build the MySQL Server part, it is unnecessary, as MySQL AB does an
excellent job to deliver optimized binaries for the mainstream
operating systems, and it is told, that the server compiled under Cygwin is
unstable.

Install MySQL (if you havn't already)
Install MySQL (if you haven't already)

=over

Expand Down Expand Up @@ -713,7 +713,7 @@ Running "make" terminates with an error message like
-o blib/arch/auto/DBD/mysql/mysql.so -shared
-L/usr/local/lib dbdimp.o mysql.o -L/usr/lib/mysql
-lmysqlclient -lm -L/usr/lib/gcc-lib/i386-redhat-linux/2.96
-lgcc -lz
-lgcc -lz
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
make: *** [blib/arch/auto/DBD/mysql/mysql.so] Error 1
Expand Down Expand Up @@ -778,13 +778,13 @@ library, for example

The use of a statically linked library is described in the
previous section on linker flags. L</Configuration>.
L</Linker flags>.
L</Linker flags>.

=item 4.)

Red Hat 8 & 9 set the Default locale to UTF which causes problems with
MakeMaker. To build DBD::mysql on these systems, do a 'unset LANG'
before runing 'perl Makefile.PL'
Red Hat 8 & 9 set the Default locale to UTF which causes problems with
MakeMaker. To build DBD::mysql on these systems, do a 'unset LANG'
before running 'perl Makefile.PL'

=back

Expand Down