Mercurial > p > roundup > code
view test/README.txt @ 5005:a86b0c02940d
Remove the tsearch2 backend
The documentation within the tsearch2 backend labels it as being
experimental and that it should not be used. The have_backend() function
in roundup.backend returns False indicating that it does not exist and
is labeled as "currently not working". The PostgreSQL website also seems
to indicate that it has been deprecated since v8.3 when text searching
was integrated into the core[1].
Considering all this, it seems like the best option is to just remove
the tsearch2 backend.
[1] http://www.postgresql.org/docs/9.4/static/tsearch2.html
| author | John Kristensen <john@jerrykan.com> |
|---|---|
| date | Sun, 11 Oct 2015 00:06:51 +1100 |
| parents | 2c3cc4ccd024 |
| children | 132d450bdc00 |
line wrap: on
line source
A number of tests uses the infrastructure of db_test_base.py grep "from db_test_base" -l *.py benchmark.py session_common.py test_anydbm.py test_indexer.py test_memorydb.py test_mysql.py test_postgresql.py test_security.py test_sqlite.py test_userauditor.py grep "import db_test_base" -l *.py test_cgi.py test_jinja2.py test_mailgw.py test_xmlrpc.py grep "import memory\|from memory" -l *.py test_mailgw.py test_memorydb.py The remaining lines are an 2001 description from Richard, which probably is outdated: Structure of the tests: 1 Test date classes 1.1 Date 1.2 Interval 2 Set up schema 3 Open with specific backend 3.1 anydbm 4 Create database base set (stati, priority, etc) 5 Perform some actions 6 Perform mail import 6.1 text/plain 6.2 multipart/mixed (with one text/plain) 6.3 text/html 6.4 multipart/alternative (with one text/plain) 6.5 multipart/alternative (with no text/plain)
