philip          Wed Jul  2 13:30:48 2003 EDT

  Modified files:              
    /phpdoc/en/faq      databases.xml 
  Log:
  Implement use of itemizedlist.
  
  
Index: phpdoc/en/faq/databases.xml
diff -u phpdoc/en/faq/databases.xml:1.19 phpdoc/en/faq/databases.xml:1.20
--- phpdoc/en/faq/databases.xml:1.19    Wed Jul  2 02:51:23 2003
+++ phpdoc/en/faq/databases.xml Wed Jul  2 13:30:48 2003
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.19 $ -->
+<!-- $Revision: 1.20 $ -->
  <chapter id="faq.databases">
   <title>Database issues</title>
   <titleabbrev>Database issues</titleabbrev>
@@ -193,28 +193,38 @@
       another.  The only change in PHP 5 is that we are no longer bundling
       the client library itself.  Some reasons in no particular order:
      </para>
-     <para>
-      1. Most systems these days already have the client library installed.
-     </para>
-     <para>
-      2. Given the above, having multiple versions of the library can get
-      messy.  For example, if you link mod_auth_mysql against one version
-      and PHP against another, and then enable both in Apache, you get a
-      nice fat crash.  Also, the bundled library didn't always play well
-      with the installed server version.  The most obvious symptom of this
-      being disagreement over where to find the mysql.socket unix domain
-      socket file.
-     </para>
-     <para>
-      3. Maintenance was somewhat lax and it was falling further and further
-      behind the released version.
-     </para>
-     <para>
-      4. Future versions of the library are under the GPL and thus we don't
-      have an upgrade path since we cannot bundle a GPL'ed library in a
-      BSD/Apache-style licensed project.  A clean break in PHP 5 seemed like
-      the best option.
-     </para>
+     <itemizedlist>
+      <listitem>
+       <para>
+        Most systems these days already have the client library installed.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Given the above, having multiple versions of the library can get
+        messy.  For example, if you link mod_auth_mysql against one version
+        and PHP against another, and then enable both in Apache, you get a
+        nice fat crash.  Also, the bundled library didn't always play well
+        with the installed server version.  The most obvious symptom of this
+        being disagreement over where to find the mysql.socket unix domain
+        socket file.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Maintenance was somewhat lax and it was falling further and further
+        behind the released version.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Future versions of the library are under the GPL and thus we don't
+        have an upgrade path since we cannot bundle a GPL'ed library in a
+        BSD/Apache-style licensed project.  A clean break in PHP 5 seemed
+        like the best option.
+       </para>
+      </listitem>
+     </itemizedlist>
      <para>
       This won't actually affect that many people.  UNIX users, at least the
       ones who know what they are doing, tend to always build PHP against



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to