... | @@ -13,6 +13,16 @@ of MariaDB, attempts to create or update the database will fail with the error ` |
... | @@ -13,6 +13,16 @@ of MariaDB, attempts to create or update the database will fail with the error ` |
|
|
|
|
|
* Some unit tests fail when using MySQL's latest release as of September 19 versioned 8.0.22. This is under investigation in #1570.
|
|
* Some unit tests fail when using MySQL's latest release as of September 19 versioned 8.0.22. This is under investigation in #1570.
|
|
|
|
|
|
|
|
## Kea 2.1.0
|
|
|
|
|
|
|
|
* The Kea documentation project hosted at https://kea.readthedocs.io/ started having build failures
|
|
|
|
in October. This was not a single occurrence and happened with multiple projects which is documented
|
|
|
|
[here](https://blog.readthedocs.com/build-errors-docutils-0-18/). It caught the release of 2.1.0 off
|
|
|
|
guard. This was fixed with #2161 in master, but to keep the `Kea-2.1.0` reflecting the released
|
|
|
|
sources, instead of moving it, `Kea-2.1.0-fix` was added. This is what the version that appears in
|
|
|
|
the Read the Docs sidebar and it should be interpreted as having `Kea-2.1.0` documentation.
|
|
|
|
In reality, it only has the documentation build fix on top.
|
|
|
|
|
|
## Kea 1.9.10 & 1.9.11
|
|
## Kea 1.9.10 & 1.9.11
|
|
|
|
|
|
* If, using configuration backend on Kea 1.9.10 or 1.9.11, you managed to add a client class with associated option data, and then removed the client class, you would be left with dangling option data rows in the database. Option data rows are now properly removed when the associated client class is removed after #2094 which was released with 2.0.0. The foreign key constraint which helps realize the cascading delete will fail to be created on upgrade to the new schema with the following error:
|
|
* If, using configuration backend on Kea 1.9.10 or 1.9.11, you managed to add a client class with associated option data, and then removed the client class, you would be left with dangling option data rows in the database. Option data rows are now properly removed when the associated client class is removed after #2094 which was released with 2.0.0. The foreign key constraint which helps realize the cascading delete will fail to be created on upgrade to the new schema with the following error:
|
... | | ... | |