Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 6804:25d08e15e3b4
issue2551224 - Replace dbm db for sessions/otks when using sqlite
Generate new sqlite db's for storing one time keys and session and
other ephemeral data.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 25 Jul 2022 15:30:36 -0400 |
| parents | b3d4b25b4922 |
| children | bdd28b244839 |
comparison
equal
deleted
inserted
replaced
| 6803:db437dd13ed5 | 6804:25d08e15e3b4 |
|---|---|
| 27 | 27 |
| 28 Contents: | 28 Contents: |
| 29 | 29 |
| 30 .. contents:: | 30 .. contents:: |
| 31 :local: | 31 :local: |
| 32 | |
| 33 .. index:: Upgrading; 2.2.0 to 2.3.0 | |
| 34 | |
| 35 Migrating from 2.2.0 to 2.3.0 | |
| 36 ============================= | |
| 37 | |
| 38 Session/OTK data storage for SQLite backend changed | |
| 39 --------------------------------------------------- | |
| 40 | |
| 41 Roundup stores a lot of ephemeral data: | |
| 42 | |
| 43 * login session tokens, | |
| 44 * rate limits | |
| 45 * password reset attempt tokens | |
| 46 * one time keys | |
| 47 * and anti CSRF keys. | |
| 48 | |
| 49 These were stored using dbm style files while the main data | |
| 50 is stored in a SQLite db. Using both dbm and sqlite style | |
| 51 files is surprising and due to how we lock dbm files can be | |
| 52 a performance issue. | |
| 53 | |
| 54 In this release two sqlite databases called ``db-otk`` and | |
| 55 ``db-session`` replace the dbm databases. Once you make the | |
| 56 change the old ``otks`` and ``sessions`` dbm databases can | |
| 57 be removed. | |
| 58 | |
| 59 Note this replacement will require users to log in again and | |
| 60 refresh web pages to save data. It is best is people save | |
| 61 all their changes and log out of Roundup before the upgrade | |
| 62 is done to minimize confusion. Because the data is | |
| 63 ephemeral, there is no plan to migrate this data to the new | |
| 64 SQLite databases. | |
| 32 | 65 |
| 33 .. index:: Upgrading; 2.1.0 to 2.2.0 | 66 .. index:: Upgrading; 2.1.0 to 2.2.0 |
| 34 | 67 |
| 35 Migrating from 2.1.0 to 2.2.0 | 68 Migrating from 2.1.0 to 2.2.0 |
| 36 ============================= | 69 ============================= |