Changes between Version 14 and Version 15 of DatabaseBackend

Timestamp:

Jan 23, 2006, 4:42:46 PM (18 years ago)

Author:

Christian Boos

Comment:

Refactored the page + added a reference to ticket #1874 (Oracle support)

DatabaseBackend

@@ -1 +1 @@
 = Database Backend =
 
-Currently, Trac uses [http://www.sqlite.org SQLite] as its database backend.
+Initially, Trac only supported SQLite for its database backend.
+Postgresql support has been added as of Trac [milestone:0.9].
 
-However, there have been several requests that other databases should be supported as well (see #126, #986).
+Since milestone:0.10, Trac offers an easily extensible layer for
+Database support (see [source:trunk/trac/db/api.py trac.db.api]).
 
-== Existing Proposals and Implementations ==
+The existing backends have been refactored and integrated in this
+layer. There's currently bundled support for:
+ * [http://www.sqlite.org SQLite], using PySqlite
+ * [http://www.postgresql.org PostgreSQL], using a variety of bindings
+   ([http://initd.org/projects/psycopg1 psycopg1], 
+   [http://initd.org/projects/psycopg2 psycopg2], or 
+   [http://pypgsql.sourceforge.net/ pyPgSQL]) (see #126 for historical notes)
 
-Postgresql is supported as of Trac 0.9.  Here are some limited instructions.
+There's some work in progress for the following:
+ * MySQL (see #986)
+ * Oracle (see #1874)
+
+== Backend Specific Installation Instructions ==
+
+=== Postgresql ===
+
  * Have a working copy of Postgresql
- * Get the proper database driver for Python - [http://initd.org/projects/psycopg1 psycopg1], [http://initd.org/projects/psycopg2 psycopg2], or [http://pypgsql.sourceforge.net/ pyPgSQL]
+ * Get the proper database driver for Python (see above)
  * Create a database for your Trac environment
 {{{
@@ -19 +34 @@
 }}}
 
-MySQL is only experimentally supported with the patch attached to ticket #986.  It also has several limitations.
+=== MySQL ===
+
+MySQL is only experimentally supported with the patch attached to ticket #986.  
+It also has several limitations.
  * Have a working copy of MySQL version 4.1.12 or greater.
  * [http://sourceforge.net/projects/mysql-python MySQLdb] - Python database driver for MySQL
@@ -38 +56 @@
 }}}
 
-== Object-Relational Mapper ==
 
-provide a unified object interface to different RDBMS
+== Alternative Ideas for Database Independence ==
 
- * SQLObject
-  I think some people have been talking about using [http://sqlobject.org SQLObject] to accomplish this goal of database independence.
+=== Object-Relational Mapper ===
 
+An ORM could be used to provide a unified object interface to different RDBMS:
+ * some people have been talking about using [http://sqlobject.org SQLObject] 
+   to accomplish this goal of database independence.
  * [http://modeling.sourceforge.net/ Modeling]
-  Another, more advanced (and more complex) OR-Mapper.
+   Another, more advanced (and more complex) OR-Mapper.
 
 Comparisions between both and more info on Python ORMs:
-
  * http://toulouse.amber.org/archives/2003/04/21/evaluating_objectrelational_migration.html
  * http://google.com/search?q=SQLObject+modeling
 
-== Store Tickets and Wiki pages directly in the Subversion repository ==
+=== Store Tickets and Wiki pages directly in the Subversion repository ===
 
 A compelling idea with many advantages. A page advocating this plan is TighterSubversionIntegration. There has also been a discussion on the Trac mailing list. All arguments from this discussion are summarized on the page [wiki:WhySQLite WhySQLite].
 
-== Other Alternatives ==
+=== Other Alternatives ===
 
-http://wiki.w4py.org/databaseintegration.html
-
-http://adodb.sourceforge.net - the fast ADODB db abstraction layer (version available for python)
+ * http://wiki.w4py.org/databaseintegration.html
+ * http://adodb.sourceforge.net - the fast ADODB db abstraction layer (version available for python)