1
0
mirror of synced 2025-01-18 06:21:40 +03:00

docbook docs update

This commit is contained in:
pookey 2007-06-01 10:18:49 +00:00
parent 2662b46e9a
commit 614ec1fb21

View File

@ -113,44 +113,46 @@
<sect1 id="features">
<title>Features</title>
<para>
General Features
</para>
<itemizedlist>
<listitem>Fully object-oriented following best practices and design patterns</listitem>
<listitem>Multiple databases</listitem>
<listitem>Database connection pooling with connection-record -registry</listitem>
<listitem>Runtime configuration (no XML needed!)</listitem>
<listitem>Very modular structure (only uses the needed features)</listitem>
<listitem>The runtime components can be compiled into a single fileM</listitem>
<listitem>Leveled configuration (attributes can be set at global, connection and table levels)</listitem>
</itemizedlist>
<para>
Database Abstraction
</para>
<itemizedlist>
<listitem>A DSN (data source name) or array format for specifying database servers</listitem>
<listitem>Datatype abstraction and on demand datatype conversion</listitem>
<listitem>supports PDO</listitem>
<listitem>Database query profiling</listitem>
<listitem>Query caching</listitem>
<listitem>Sequence / autoincrement emulation</listitem>
<listitem>Replace emulation</listitem>
<listitem>RDBMS management methods (creating, dropping, altering)</listitem>
<listitem>SQL function call abstraction</listitem>
<listitem>SQL expression abstraction</listitem>
<listitem>Pattern matching abstraction</listitem>
<listitem>Portable error codes</listitem>
<listitem>Nested transactions</listitem>
<listitem>Transaction isolation abstraction</listitem>
<listitem>Transaction savepoint abstraction</listitem>
<listitem>Index/Unique Key/Primary Key support</listitem>
<listitem>Ability to read the information schema</listitem>
<listitem>Reverse engineering schemas from an existing database</listitem>
<listitem>LIMIT / OFFSET emulation </listitem>
</itemizedlist>
<sect3 id="features-general">
<title>
General Features
</title>
<itemizedlist>
<listitem>Fully object-oriented following best practices and design patterns</listitem>
<listitem>Multiple databases</listitem>
<listitem>Database connection pooling with connection-record -registry</listitem>
<listitem>Runtime configuration (no XML needed!)</listitem>
<listitem>Very modular structure (only uses the needed features)</listitem>
<listitem>The runtime components can be compiled into a single fileM</listitem>
<listitem>Leveled configuration (attributes can be set at global, connection and table levels)</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>
Database Abstraction
</title>
<itemizedlist>
<listitem>A DSN (data source name) or array format for specifying database servers</listitem>
<listitem>Datatype abstraction and on demand datatype conversion</listitem>
<listitem>supports PDO</listitem>
<listitem>Database query profiling</listitem>
<listitem>Query caching</listitem>
<listitem>Sequence / autoincrement emulation</listitem>
<listitem>Replace emulation</listitem>
<listitem>RDBMS management methods (creating, dropping, altering)</listitem>
<listitem>SQL function call abstraction</listitem>
<listitem>SQL expression abstraction</listitem>
<listitem>Pattern matching abstraction</listitem>
<listitem>Portable error codes</listitem>
<listitem>Nested transactions</listitem>
<listitem>Transaction isolation abstraction</listitem>
<listitem>Transaction savepoint abstraction</listitem>
<listitem>Index/Unique Key/Primary Key support</listitem>
<listitem>Ability to read the information schema</listitem>
<listitem>Reverse engineering schemas from an existing database</listitem>
<listitem>LIMIT / OFFSET emulation </listitem>
</itemizedlist>
</sect3>
<sect3 id="features-orm">
<title>
Object Relational Mapping
@ -218,10 +220,16 @@
<title>Requirements</title>
<para>
Doctrine requires PHP >= 5.1, and it doesn't require any external libraries.
It runs on both windows and *nix based platforms.
</para>
<para>
For database abstraction Doctrine uses PDO which is bundled with php by
default. Doctrine also requires a little adodb-hack for table creation,
default. You will need PDO support for whatever database you intend to
use, and if you want to be able to run the included unit tests, you
will need SQLite support.
</para>
<para>
Doctrine also requires a little adodb-hack for table creation,
which comes with doctrine.
</para>
</sect1>
@ -229,15 +237,8 @@
<sect1 id="community">
<title>Community</title>
<para>
Doctrine has 3 mailing lists, an IRC channel, a forum, and a wiki.
Doctrine has 3 mailing lists, an IRC channel, a forum, and a wiki/trac.
</para>
<sect2 id="community-forum">
<title>Forum</title>
<para>
The Doctrine forum can be found here:
<ulink url="http://www.phpbbserver.com/phpdoctrine/">http://www.phpbbserver.com/phpdoctrine/</ulink>
</para>
</sect2>
<sect2 id="community-mailinglist">
<title>Mailing Lists</title>
<para>
@ -273,6 +274,13 @@
url="http://doctrine.pengus.net/trac">http://doctrine.pengus.net/trac</ulink>
</para>
</sect2>
<sect2 id="community-forum">
<title>Forum</title>
<para>
The Doctrine forum can be found here:
<ulink url="http://www.phpbbserver.com/phpdoctrine/">http://www.phpbbserver.com/phpdoctrine/</ulink>
</para>
</sect2>
</sect1>
<sect1 id="contributing">