Changes between Version 18 and Version 19 of DatabaseBackend

Timestamp:

Apr 7, 2006, 3:15:48 PM (18 years ago)

Author:

Christian Boos

Comment:

Note about unicode issue with psycopg1

DatabaseBackend

@@ -1 +1 @@
 = Database Backend =
 
-Initially, Trac only supported SQLite for its database backend.
+Initially, Trac only supported SQLite for its database backend (see PySqlite).
+
 Postgresql support has been added as of Trac [milestone:0.9].
 
-Since milestone:0.10, Trac offers an easily extensible layer for
+Mysql support will be added for Trac [milestone:0.10]
+(see this [http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/342/focus=348 status report]).
+
+More generally, since milestone:0.10, Trac offers an easily extensible layer for
 Database support (see [source:trunk/trac/db/api.py trac.db.api]).
 
@@ -11 +15 @@
  * [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/psycopg1 psycopg1] (but see below)'', 
    [http://initd.org/projects/psycopg2 psycopg2], or 
    [http://pypgsql.sourceforge.net/ pyPgSQL]) (see #126 for historical notes)
@@ -37 +41 @@
 
 For a postgresql recipe tested on CentOS4 (Red Hat -EL4) see [wiki:PostgresqlRecipe].
+
+Note that with the recent switch to using unicode internally, 
+there seems to be some issues with psycopg1, whereas pgsql and psycopg2 
+seem to do fine (see #2907).
 
 === MySQL ===