Mercurial > p > roundup > code
comparison doc/installation.txt @ 7719:3071db43bfb6
feat: issue2550852 - support using a specified PostgreSQL db schema
Finally after 7 years this is closed.
roundup/backends/back_postgresql.py:
Support use of schema when specified in RDBMS_NAME. Stuart McGraws
code is finally merged 8-).
test/test_postgresql.py, test/conftest.py:
Run all postgresql tests in the schema db as well.
Also make sure that db_nuke raises an error when trying to delete
the schema test database. Conftest defines pg_schema mark that can
be used to exclude schema tests with pytest -m "not pg_schema".
roundup/configuration.py:
change doc on RDBMS_NAME to include db.schema form.
.travis.yml, .github/workflows/ci-test.yml:
create schema test db; add user for testing with schema; grant new
user create privs for schema.
doc/installation.txt:
Reference to roundup-admin init deleting schema added.
doc/mysql.txt doc/postgresql.txt:
New documentation on psql/mysql commands to set up a production db.
doc/upgrading.txt:
mention schema support, also document service setting for
selecting connection from pg_service.conf.
doc/reference.txt:
update config.ini documentation for RDBMS_NAME.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 27 Dec 2023 22:52:14 -0500 |
| parents | a03f8f681992 |
| children | 68c04cc8edf7 |
comparison
equal
deleted
inserted
replaced
| 7718:3da452f4a3ac | 7719:3071db43bfb6 |
|---|---|
| 476 prompted:: | 476 prompted:: |
| 477 | 477 |
| 478 Admin Password: | 478 Admin Password: |
| 479 Confirm: | 479 Confirm: |
| 480 | 480 |
| 481 Note: running this command will *destroy any existing data in the | 481 Note: running this command will *destroy any existing data in |
| 482 database*. In the case of MySQL and PostgreSQL, any existing database | 482 the database*. In the case of MySQL and PostgreSQL, any existing |
| 483 will be dropped and re-created. | 483 database (or optionally database schema for PostgreSQL) will be |
| 484 dropped and re-created. | |
| 484 | 485 |
| 485 Once this is done, the tracker has been created. See the note in | 486 Once this is done, the tracker has been created. See the note in |
| 486 the `administration guide`_ on how to :ref:`initialise a | 487 the `administration guide`_ on how to :ref:`initialise a |
| 487 tracker without being prompted for the password <initpw>` or | 488 tracker without being prompted for the password <initpw>` or |
| 488 exposing the password on the command line. | 489 exposing the password on the command line. |