Mercurial > p > roundup > code
comparison doc/upgrading.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 | 0c855080794e |
| children | 8147f6deac9f |
comparison
equal
deleted
inserted
replaced
| 7718:3da452f4a3ac | 7719:3071db43bfb6 |
|---|---|
| 150 | 150 |
| 151 The removed columns are: severity, versions, keywords, dependencies. | 151 The removed columns are: severity, versions, keywords, dependencies. |
| 152 | 152 |
| 153 It is also missing the ``solves`` field which is added to match the | 153 It is also missing the ``solves`` field which is added to match the |
| 154 schema. | 154 schema. |
| 155 | |
| 156 New PostgreSQL Settings (optional) | |
| 157 ---------------------------------- | |
| 158 | |
| 159 With this release, you can specify a Postgresql database | |
| 160 schema to use. By default Roundup creates a database when | |
| 161 using ``roundup-admin init``. Setting the rdbms ``name`` | |
| 162 keyword to ``roundup_database.roundup_schema`` will create | |
| 163 and use the ``roundup_schema`` in the pre-created | |
| 164 ``roundup_database``. | |
| 165 | |
| 166 Also there is a new configuration keyword in the rdbms section of | |
| 167 ``config.ini``. The ``service`` keyword allows you to define the | |
| 168 service name for Postgres that will be looked up in the Postgres | |
| 169 `Connection Service File`_. Setting service to `roundup` with the | |
| 170 following in the service file:: | |
| 171 | |
| 172 [roundup_roundup] | |
| 173 host=127.0.0.1 | |
| 174 port=5432 | |
| 175 user=roundup | |
| 176 password=roundup | |
| 177 dbname=roundup | |
| 178 | |
| 179 would use the roundup database with the specified credentials. | |
| 180 | |
| 181 It is possible to define a service that connects to a specific | |
| 182 schema. However this will require a little fiddling to get things | |
| 183 working. A future enhancement may make using a schema via this | |
| 184 mechanism easier. See https://issues.roundup-tracker.org/issue2551299 | |
| 185 for details. | |
| 186 | |
| 187 .. _`Connection Service File`: https://www.postgresql.org/docs/current/libpq-pgservice.html | |
| 155 | 188 |
| 156 Bad Login Rate Limiting and Locking (info) | 189 Bad Login Rate Limiting and Locking (info) |
| 157 ------------------------------------------ | 190 ------------------------------------------ |
| 158 | 191 |
| 159 Brute force logins have been rate limited in the HTML web interface | 192 Brute force logins have been rate limited in the HTML web interface |