Summary: Support selecion session/otk data store. Add redis as data store. Allow admin to select the backend data store. Compatibility matrix: main\/ session>| anydbm | sqlite | redis | mysql | postgresql | anydbm | D | | X | | | sqlite | X | D | X | | | mysql | | | | D | | postgresql | | | | | D | --------------------------------------------------------------+ D - default if unconfigured, X - compatible choice DETAILS roundup/configuration.py: add config.ini section sessiondb with settings: backend and redis_url. CHANGES.txt, doc/admin_guide.txt, doc/installation.txt, doc/upgrading.txt: doc on config of session db and redis. Plus some other fixes: admin - clarified why we do not drop __words and __testids table in native-fts conversion. TYpo fix. upgrading - doc how you can keep using anydbm for session data with sqlite. Fix dupe sentence in an upgrading config.ini section. roundup/backends/back_anydbm.py, roundup/backends/back_sqlite.py: code to support redis, redis/anydbm backends respectively. roundup/backends/sessions_redis.py new storage backend for redis. roundup/rest.py, roundup/cgi/actions.py, roundup/cgi/templating.py redis uses a different way of calculating lifetime/timestamp. Since expiration of an item occurred if its timestamp was more than 1 week old, code would calculate: now - 1 week + lifetime. But this results in faster expiration in redis if used for lifetime/timestamp. Convert code to use the lifetime() method in BasicDatabase that generates the right timestamp for each backend. test/session_common.py: added tests for more cases, get without default, getall non-existing key etc. timestamp test changed to use new self.get_ts which is overridden in other tests. Test that datatypes survive storage. test/test_redis_session.py: test redis session store with sqlite and anydbm primary databases test/test_anydbm.py, test/test_sqlite.py add test to make sure the databases are properly set up sqlite - add test cases where anydbm is used as datastore anydbm - remove updateTimestamp override add get_ts(). test/test_config.py tests on redis_url and compatibility on choice of sessiondb backend .travis.yml: add redis db and redis-py

.. meta::
    :description:
        Definitions of terms used in the Roundup Issue Tracker
	documentation.

================
Roundup Glossary
================


class
   a definition of the properties and behaviour of a set of items
classname
   the name of a class. It must start with a letter, end with a letter
   or "_", and only have alphanumerics and "_" in the middle.
db (or hyperdb)
   a collection of items
designator
   a combined class + itemid reference to any item in the
   hyperdb. E.g. issue26. Note that form values can include
   something that looks like a designator composed of a classname, a
   dash '-', and a number. E.g. file-1. These
   are used to create new instances of a class via the web interface.
itemid
   a numeric reference to a particular item of one class
item
   a collection of data that forms one entry in the hyperdb.
property
   one element of data that makes up an item. In Roundup, the set 
   of item properties may be changed as needed - even after the 
   tracker has been initialised and used in production.
schema
   the definition of all the classes that make up an tracker
tracker
   the schema and hyperdb that forms one issue tracker
tracker home
   the physical location on disk of a tracker


-----------------

Back to `Table of Contents`_

.. _`Table of Contents`: index.html