Author: mjevans
Date: Wed Jun 30 12:29:18 2010
New Revision: 14213
Modified:
dbi/trunk/lib/DBI/DBD/Metadata.pm
Log:
more grammar changes
Modified: dbi/trunk/lib/DBI/DBD/Metadata.pm
==============================================================================
--- dbi/trunk/lib/DBI/DBD/Metadata.pm (original)
+++ dbi/trunk/lib/DBI/DBD/Metadata.pm Wed Jun 30 12:29:18 2010
@@ -33,13 +33,13 @@
ODBC driver and use it to generate code and data to use in your own
DBI driver for the same database.
-For generating code to support the get_info method:
+To generate code to support the get_info method:
perl -MDBI::DBD::Metadata -e "write_getinfo_pm('dbi:ODBC:dsn-name','user','pass','Driver')"
perl -MDBI::DBD::Metadata -e write_getinfo_pm dbi:ODBC:foo_db username password Driver
-For generating code to support the type_info method:
+To generate code to support the type_info method:
perl -MDBI::DBD::Metadata -e "write_typeinfo_pm('dbi:ODBC:dsn-name','user','pass','Driver')"
@@ -48,7 +48,7 @@
Where C<dbi:ODBC:dsn-name> is the connection to use to extract the
data, and C<Driver> is the name of the driver you want the code
generated for (the driver name gets embedded into the output in
-many places).
+numerous places).
=head1 Generating a GetInfo package for a driver
@@ -58,13 +58,13 @@
This method generates a DBD::Driver::GetInfo package from the data
source you specified in the parameter list or in the environment
variable DBI_DSN.
-DBD::Driver::GetInfo should help a DBD author implementing the DBI
+DBD::Driver::GetInfo should help a DBD author implement the DBI
get_info() method.
-Because you are just creating this package, it's very unlikely that
+Because you are just creating this package, it is very unlikely that
DBD::Driver already provides a good implementation for get_info().
Thus you will probably connect via DBD::ODBC.
-Once you are sure that it is producing semi-sane data, you would
+Once you are sure that it is producing reasonably sane data, you should
typically redirect the standard output to lib/DBD/Driver/GetInfo.pm, and
then hand edit the result.
Do not forget to update your Makefile.PL and MANIFEST to include this as
@@ -79,7 +79,7 @@
values directly in the %info hash.
A few examples show the use of CODE references and the implementation
via subroutines.
-It is very likely that you have to write additional subroutines for
+It is very likely that you will have to write additional subroutines for
values depending on the session state or server version, e.g.
SQL_DBMS_VER.
@@ -227,7 +227,7 @@
The user and pass parameters are the other optional connection
parameters that will be provided to the DBI connect method.
-Once you are sure that it is producing semi-sane data, you would
+Once you are sure that it is producing reasonably sane data, you should
typically redirect the standard output to lib/DBD/Driver/TypeInfo.pm,
and then hand edit the result if necessary.
Do not forget to update your Makefile.PL and MANIFEST to include this as
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.