Mercurial > p > roundup > code
view test/README.txt @ 5086:2b551b6b0830
issue2550549 Postgres error on message templating
Exception gets thrown and not captured if nodeid is too large on
postgres. Added a check in rdbms_common layer that max nodeid is <
2^31 -1. This is also the limit for INTEGER on MySql. SqlLite can
support up to 2^63-1, but I chose the smallest common denominator.
Large nodeid should now returns no such id rather than a stack trace.
Patch idea from: martin.v.loewis. (John Rouillard)
This fixes the reason for patches:
https://hg.python.org/tracker/roundup/rev/1548763e8273
and
https://hg.python.org/tracker/roundup/rev/eb3be57f1ef2
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 18 Jun 2016 22:48:21 -0400 |
| parents | a86b0c02940d |
| 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)
