|
| 1 | +ietfdb (6.98.0) ietf; urgency=medium |
| 2 | + |
| 3 | + **Refactoring of the primary index type for Document and DocAlias objects** |
| 4 | + |
| 5 | + This release contains a series of 216 migration steps that changes the |
| 6 | + Document and DocAlias primary keys from character strings to integers, and |
| 7 | + makes corresponding code changes. |
| 8 | + |
| 9 | + This was prompted by database limitations discovered when trying to make |
| 10 | + DocAlias use a m2m document field; with 255 long strings as primary keys for |
| 11 | + Document and DocAlias this violated the MySQL database limitations. |
| 12 | + |
| 13 | + Changing the primary keys to integers should also improve efficiency. |
| 14 | + |
| 15 | + Additionally, in order to make it possible to have DocAlias objects referring |
| 16 | + to multiple documents, in order to reflect STD and BCP names that refer to |
| 17 | + multiple RFCs, DocAlias has been refactored to use many-to-many tables instead |
| 18 | + of foreign keys do toduments. |
| 19 | + |
| 20 | + Due to the data migrations which create the new integer primary keys and adds |
| 21 | + corresponding integer foreign keys matching the previous string foreign keys |
| 22 | + in all tables having foreign keys to Document and DocAlias, some of these |
| 23 | + migrations take a long time. The total set of migrations are expected to have |
| 24 | + a runtime on the order of 2 hours. |
| 25 | + |
| 26 | + This release is scheduled to be deployed on 16 Jun 2019 at 16:00 UTC, with |
| 27 | + an expected datatracker downtime, for safety backup and application of the |
| 28 | + migrations to run, of about 3 hours. |
| 29 | + |
| 30 | + -- Henrik Levkowetz <henrik@levkowetz.com> 16 Jun 2019 14:16:12 +0000 |
| 31 | + |
| 32 | + |
1 | 33 | ietfdb (6.97.1) ietf; urgency=medium |
2 | 34 |
|
3 | 35 | This is a bugfix release which clears the way for the upcoming major |
|
0 commit comments