Changes between Version 11 and Version 12 of DatabaseBackend

Timestamp:

Sep 30, 2005, 8:56:34 PM (19 years ago)

Author:

brad <brad@…>

Comment:

—

DatabaseBackend

@@ -7 +7 @@
 == Existing Proposals and Implementations ==
 
- * There has been an attempt to provide support for [http://www.postgresql.org PostgreSQL]: source:/branches/rocky-dev/features/postgresql_support/ though this branch is not so active this days...
+Postgresql is supported as of Trac 0.9.  Here are some limited instructions.
+ * 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]
+ * Create a database for your Trac environment
+{{{
+% createdb dbname
+}}}
+ * Run trac-admin to create a new Trac environment.  When prompted for a Database connection string, use:
+{{{
+postgres://user:pass@localhost:5432/dbname
+}}}
 
- * A more recent PostgreSQL effort is [http://trac.dsource.org/projects/test/wiki/PostgresqlPatch here].
-
- * Data Model Change
-  If SQLObject (see below) works well, this proposal may not be necessary, but I would like some feedback (brad at dsource dot org) on the following proposal:  [http://trac.dsource.org/projects/test/wiki/TracTicketDataModelChanges TracTicketDataModelChanges]
-
-  I like its elegance in handling custom fields, allowing multiple ticket attributes per ticket (i.e. the ability to indicate all the versions of the software that a bug is present in, rather than being limited to indicating a single version), and I imagine it results in reduced code overall for the app because of the use of metadata.
 
 == Object-Relational Mapper ==