Mercurial > p > roundup > code
view doc/postgresql.txt @ 5133:85eee1f236b2
I had an incorrect fix for issue2550601. Changed schema to define
class patches not patch.
Changed commented out patches section in bug.item.html to
use patches-1 an not patch-1 as a result of schema changes.
The show open Milestones link had a leak of the @group
value. If you clicked on show open tasks or show open bugs
they group by priority.
The url being formed for show open milestones was inheriting the @group
if you were on an index page for bugs or milestones. Explicit set the
@group to status (which a milestone does have) prevents the
@group=priority from being applied to a milestone index page which
results in a red error banner stating priority is an invalid param for
milestones.
./demo.py -t devel now runs without obvious breakage.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 04 Jul 2016 18:19:51 -0400 |
| parents | 76b71c9bd50d |
| children | e48b039b0ec0 |
line wrap: on
line source
========================== PostgreSQL/psycopg Backend ========================== This are notes about PostqreSQL backend based on the psycopg adapter for Roundup issue tracker. Prerequisites ============= To use PostgreSQL as backend for storing roundup data, you should additionally install: 1. PostgreSQL 8.x or higher - http://www.postgresql.org/ 2. The psycopg python interface to PostgreSQL: http://initd.org/software/initd/psycopg Running the PostgreSQL unit tests ================================= The user that you're running the tests as will need to be able to access the postgresql database on the local machine and create and drop databases. See the config values in 'test/db_test_base.py' about which database connection, name and user will be used. Credit ====== The postgresql backend was originally submitted by Federico Di Gregorio <fog@initd.org>