Mercurial > p > roundup > code
view doc/mysql.txt @ 5133:85eee1f236b2
I had an incorrect fix for issue2550601. Changed schema to define
class patches not patch.
Changed commented out patches section in bug.item.html to
use patches-1 an not patch-1 as a result of schema changes.
The show open Milestones link had a leak of the @group
value. If you clicked on show open tasks or show open bugs
they group by priority.
The url being formed for show open milestones was inheriting the @group
if you were on an index page for bugs or milestones. Explicit set the
@group to status (which a milestone does have) prevents the
@group=priority from being applied to a milestone index page which
results in a red error banner stating priority is an invalid param for
milestones.
./demo.py -t devel now runs without obvious breakage.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 04 Jul 2016 18:19:51 -0400 |
| parents | 33a1f03b9de0 |
| children | 98fdc1f98194 |
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 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``).
