Mercurial > p > roundup > code
view doc/mysql.txt @ 5277:b580f61929e2
Removing richard from notification list. Verified that
he doesn't want to be on it anymore.
Date: Sun, 24 Sep 2017 14:58:24 +1000
To: rouiljsomewhere
From: Richard Jones <r1chardj0n3s at gmail.com>
Subject: Re: Do you still want new issues to roundup tracker sent to
you?
--94eb2c0da3aac771bb0559e84afb
Content-Type: text/plain; charset="UTF-8"
Thanks John, yes please do remove me.
Richard
On 24 September 2017 at 14:13, John P. Rouillard <rouilj at cs.umb.edu>
wrote:
> Hi Richard:
>
> I am working on updating the roundup tracker to
> get it ready for the current development code.
>
> As I was testing I noticed you are still in the
> list of email addresses getting new issue emails.
>
> Do you want to continue to receive these since
> you aren't actively developing roundup?
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 24 Sep 2017 18:44:48 -0400 |
| parents | 98fdc1f98194 |
| children | e2978ed3b550 64ceb9c14b28 |
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 - http://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 - http://sourceforge.net/projects/mysql-python 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 http://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``).
