nlopess Mon Feb 23 10:38:39 2004 EDT
Modified files:
/phpdoc/en/faq databases.xml
Log:
better docbook tag and livedocs compliance
http://cvs.php.net/diff.php/phpdoc/en/faq/databases.xml?r1=1.23&r2=1.24&ty=u
Index: phpdoc/en/faq/databases.xml
diff -u phpdoc/en/faq/databases.xml:1.23 phpdoc/en/faq/databases.xml:1.24
--- phpdoc/en/faq/databases.xml:1.23 Sat Dec 20 23:21:40 2003
+++ phpdoc/en/faq/databases.xml Mon Feb 23 10:38:38 2004
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.23 $ -->
+<!-- $Revision: 1.24 $ -->
<chapter id="faq.databases">
<title>Database issues</title>
<titleabbrev>Database issues</titleabbrev>
@@ -59,13 +59,15 @@
built in drivers), or to use an intermediary file format that Access
and PHP both understand, such as flat files or dBase databases.
On this point Tim Hayes from OpenLink software writes:
- <programlisting>
- Using another database as an intermediary is not a good idea, when you can
- use ODBC from PHP straight to your database - i.e. with OpenLink's drivers. If
- you do need to use an intermediary file format, OpenLink have now released
- Virtuoso (a virtual database engine) for NT, Linux and other Unix platforms.
- Please visit our <ulink url="&url.openlink;">website</ulink> for a free
download.
- </programlisting>
+ <blockquote>
+ <para>
+ Using another database as an intermediary is not a good idea, when you can
+ use ODBC from PHP straight to your database - i.e. with OpenLink's drivers. If
+ you do need to use an intermediary file format, OpenLink have now released
+ Virtuoso (a virtual database engine) for NT, Linux and other Unix platforms.
+ Please visit our <ulink url="&url.openlink;">website</ulink> for a free
download.
+ </para>
+ </blockquote>
</para>
<para>
One option that has proved successful is to use MySQL and its
