Mercurial > p > roundup > code
view doc/mysql.txt @ 6160:9619d64c0351
Doc updates for customizing.txt, start of index generation
customizing.txt:
fix doc on schema.py. Documented obsolete db schema
declaration/initial data method.
doc on config.ini is incomplete. doc as such. Add doc for [rdbms]:
backend, cache_size, sqlite_timeout
document Interval schema type. Also change formatting for list of
schema types to description list from regular list so types are more
visible.
add link to roundup wiki for schema chnge examples.
fix formatting for postfix config.
document Rest Access and Xmlrpc Access permissions; change classic
schema.py example to include them.
doc db/backend_name as obsolete, conf.py [rdbms] backend used
instead.
start adding index references
conf.py: update copyright year
index.txt: add link to genindex.html.
_templates/layout.html: change code to make index output work. Not
sure what the change does, just monkey pasting from
sphinx basic/layout.html
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 11 May 2020 00:02:31 -0400 |
| parents | e48b039b0ec0 |
| children | c2fd254c9257 |
line wrap: on
line source
============= MySQL Backend ============= This notes detail the MySQL backend for the Roundup issue tracker. Prerequisites ============= To use MySQL as the backend for storing roundup data, you also need to install: 1. MySQL RDBMS 4.0.18 or higher - https://www.mysql.com/. Your MySQL installation MUST support InnoDB tables (or Berkeley DB (BDB) tables if you have no other choice). If you're running < 4.0.18 (but not <4.0) then you'll need to use BDB to pass all unit tests. Edit the ``roundup/backends/back_mysql.py`` file to enable DBD instead of InnoDB. 2. Python MySQL interface - https://pypi.org/project/mysqlclient/ Other Configuration =================== If you are indexing large documents (e.g attached file contents) using MySQL, you may need to increase the max_allowed_packet size. If you don't you can see the error:: 'MySql Server has gone away (2006)' To do this edit /etc/my.conf and change:: [mysqld] max_allowed_packet = 1M the 'max_allowed_packet' value from '1M' to '64M' or larger. Alternatively you can install an alternate indexer (whoosh, xapian etc.) and force the tracker to use it by setting the ``indexer`` setting in the tracker's ``config.ini``. This fix was supplied by telsch. See issue https://issues.roundup-tracker.org/issue2550743 for further info or if you are interested in developing a patch to roundup to help work around this issue. Running the MySQL tests ======================= Roundup tests expect an empty MySQL database. Two alternate ways to provide this: 1. If you have root permissions on the MySQL server, you can create the necessary database entries using the follwing SQL sequence. Use ``mysql`` on the command line to enter:: CREATE DATABASE rounduptest; USE rounduptest; GRANT ALL PRIVILEGES ON rounduptest.* TO rounduptest@localhost IDENTIFIED BY 'rounduptest'; FLUSH PRIVILEGES; 2. If your administrator has provided you with database connection info, see the config values in 'test/db_test_base.py' about which database connection, name and user will be used. The MySQL database should not contain any tables. Tests will not drop the database with existing data. Showing MySQL who's boss ======================== If things ever get to the point where that test database is totally hosed, just:: $ su - # /etc/init.d/mysql stop # rm -rf /var/lib/mysql/rounduptest # /etc/init.d/mysql start and all will be better (note that on some systems, ``mysql`` is spelt ``mysqld``).
