Mercurial > p > roundup > code
view doc/postgresql.txt @ 7359:3a98a81c6e57
Reorg multiple sections
consolidate what you can/can't do to the schema into one section and
move to the top of the Tracker Schema section.. Also outline how you
*can* change the type of a property.
In the "Classes and Properties - creating a new information store
section", add new Method subsection after Properties subsection. Place
all 4 method sections in there moving them from below.
Move IssueClass section before FileClass section because IssueClass
incorporates links to FileClass not the other way around.
Fix indexes.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Tue, 16 May 2023 02:33:39 -0400 |
| parents | a0a100453eb9 |
| children | b21ebabeb2ef |
line wrap: on
line source
.. index:: postgres; deployment notes ========================== 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 2. The psycopg_ python interface to PostgreSQL_ Note that you currently need at least version 2.8 of psycopg_ -- the postgresql backend will work with 2.7 but if you're using the native postgresql indexer you need at least 2.8. Also if you want to run the tests, these also need 2.8. If your distribution has an older version we suggest that you install into a python virtual environment. .. _psycopg: https://www.psycopg.org/ .. _PostgreSQL: https://www.postgresql.org/ 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>