gwynne Wed Jun 6 05:20:48 2007 UTC
Modified files:
/phpdoc/en/internals/pdo building.xml error-handling.xml
implementing.xml index.xml intro.xml
pdo-dbh-t.xml pdo-stmt-t.xml
preparation.xml prerequisites.xml
Log:
- Fixed several spelling and grammatical errors in the PDO documentation.
- Removed displayed author information from the PDO documentation front page.
http://cvs.php.net/viewvc.cgi/phpdoc/en/internals/pdo/building.xml?r1=1.3&r2=1.4&diff_format=u
Index: phpdoc/en/internals/pdo/building.xml
diff -u phpdoc/en/internals/pdo/building.xml:1.3
phpdoc/en/internals/pdo/building.xml:1.4
--- phpdoc/en/internals/pdo/building.xml:1.3 Sat Mar 3 22:31:02 2007
+++ phpdoc/en/internals/pdo/building.xml Wed Jun 6 05:20:48 2007
@@ -1,18 +1,18 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.3 $ -->
+<!-- $Revision: 1.4 $ -->
<sect1 id="internals.pdo.building">
<title>Building</title>
<para>
The build process is designed to work with PEAR (see <ulink
url="&url.php.pear;"/> for more information about
PEAR). There are two files that are used to assist in configuring your
- package for building. The first is config.m4 which is the autoconf
- configuration file for all platforms except Win32. The second is config.w32
- which a build configuration file for use on Win32. Skeleton files for
- these are built for you when you first set up your project. You then need
- to customize them to fit the needs of your project. Once you've customized
- your config files, you can build your driver using the following sequence
- of commands:
+ package for building. The first is config.m4 which is the
+ <command>autoconf</command> configuration file for all platforms except
+ Win32. The second is config.w32 which is a build configuration file for use
+ on Win32. Skeleton files for these are built for you when you first set up
+ your project. You then need to customize them to fit the needs of your
+ project. Once you've customized your config files, you can build your driver
+ using the following sequence of commands:
</para>
<para>
http://cvs.php.net/viewvc.cgi/phpdoc/en/internals/pdo/error-handling.xml?r1=1.2&r2=1.3&diff_format=u
Index: phpdoc/en/internals/pdo/error-handling.xml
diff -u phpdoc/en/internals/pdo/error-handling.xml:1.2
phpdoc/en/internals/pdo/error-handling.xml:1.3
--- phpdoc/en/internals/pdo/error-handling.xml:1.2 Tue Oct 4 19:55:07 2005
+++ phpdoc/en/internals/pdo/error-handling.xml Wed Jun 6 05:20:48 2007
@@ -1,16 +1,16 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
<sect1 id="internals.pdo.error-handling">
<title>Error handling</title>
<para>
Error handling is implemented using a hand-shaking protocol between
PDO and the database driver code. The database driver code
- signals PDO than an error has occurred via a failure
+ signals PDO that an error has occurred via a failure
(<literal>0</literal>) return from any of the interface functions. If a zero
- is returned, the field <parameter>error_code</parameter> in the control
block appropriate to the
- context (either the pdo_dbh_t or pdo_stmt_t block). In practice, it is
- probably a good idea to set the field in both blocks to the same value to
- ensure the correct one is getting used.
+ is returned, set the field <parameter>error_code</parameter> in the control
+ block appropriate to the context (either the pdo_dbh_t or pdo_stmt_t block).
+ In practice, it is probably a good idea to set the field in both blocks to
+ the same value to ensure the correct one is getting used.
</para>
<para>
@@ -39,7 +39,7 @@
</listitem>
<listitem>
<para>
- A descriptive string. This string can contain anything additional
+ A descriptive string. This string can contain any additional
information related to the failure. Database drivers typically include
information such as an error message, code location of the failure, and
any additional descriptive information the driver developer feels
http://cvs.php.net/viewvc.cgi/phpdoc/en/internals/pdo/implementing.xml?r1=1.2&r2=1.3&diff_format=u
Index: phpdoc/en/internals/pdo/implementing.xml
diff -u phpdoc/en/internals/pdo/implementing.xml:1.2
phpdoc/en/internals/pdo/implementing.xml:1.3
--- phpdoc/en/internals/pdo/implementing.xml:1.2 Thu Dec 8 12:10:51 2005
+++ phpdoc/en/internals/pdo/implementing.xml Wed Jun 6 05:20:48 2007
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
<sect1 id="internals.pdo.implementing">
<title>Fleshing out your skeleton</title>
<sect2>
@@ -207,7 +207,7 @@
<note>
<para>
Despite being documented here, the PDO driver interface does not specify
- that his function be present; it is merely a convenient way to handle
+ that this function be present; it is merely a convenient way to handle
errors, and it just happens to be equally convenient for the majority of
database client library APIs to structure your driver implementation in
this way.
@@ -354,14 +354,14 @@
</para>
<para>
One very important responsibility of this function is the processing of SQL
- statement parameters. At the time of this call, PDO does not if your driver
- supports binding parameters into prepared statements, nor does it know if
- it supports named or positional parameter naming conventions.
+ statement parameters. At the time of this call, PDO does not know if your
+ driver supports binding parameters into prepared statements, nor does it
+ know if it supports named or positional parameter naming conventions.
</para>
<para>
Your driver is responsible for setting
<literal>stmt->supports_placeholders</literal> as appropriate for the
- underlying database. This may involved some run-time determination on the
+ underlying database. This may involve some run-time determination on the
part of your driver, if this setting depends on the version of the database
server to which it is connected. If your driver doesn't directly support
both named and positional parameter conventions, you should use the
@@ -399,7 +399,7 @@
<constant>PDO_PLACEHOLDER_NONE</constant>. If the driver doesn't support
prepare statements at all, then this function should simply allocate any state
that it might need, and then return:
</para>
<example>
- <title>implementing preparer for drivers that don't support native
prepared statements</title>
+ <title>Implementing preparer for drivers that don't support native
prepared statements</title>
<programlisting role="c"><