Mercurial > p > roundup > code
view doc/mysql.txt @ 5026:8853f422fb62
Preparing 1.5.1 steps 4/16
4. python setup.py check failed
doc/announcement.txt contains non-ascii: 'ascii' codec can't encode character u'\xe9' in position 6698: ordinal not in range(128)
It was hard to find u'\xe9', because setup.py encoded text
to 'utf8' before final check. After removing encoding step:
doc/announcement.txt contains non-ascii: 'ascii' codec can't decode byte 0xc3 in position 6698: ordinal not in range(128)
Which is fixed. Also fixed reST warning caused by |u symbol:
warning: check: Inline substitution_reference start-string without end-string. (line 156)
| author | anatoly techtonik <techtonik@gmail.com> |
|---|---|
| date | Mon, 11 Jan 2016 19:44:02 +0300 |
| 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``).
