You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: externals/libmdbx/ChangeLog.md
+28-3Lines changed: 28 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,6 @@
1
1
ChangeLog
2
2
---------
3
3
4
-
## v0.11.x (in development)
5
-
6
4
### TODO
7
5
8
6
-[Engage an "overlapped I/O" on Windows](https://github.com/erthink/libmdbx/issues/224).
@@ -20,7 +18,34 @@ ChangeLog
20
18
- Packages for [Astra Linux](https://astralinux.ru/), [ALT Linux](https://www.altlinux.org/), [ROSA Linux](https://www.rosalinux.ru/), etc.
21
19
22
20
23
-
## v0.10.5 at 2021-10-13
21
+
## v0.11.1 at 2021-10-23
22
+
23
+
### Backward compatibility break:
24
+
25
+
The database format signature has been changed to prevent
26
+
forward-interoperability with an previous releases, which may lead to a
27
+
[false positive diagnosis of database corruption](https://github.com/erthink/libmdbx/issues/238)
28
+
due to flaws of an old library versions.
29
+
30
+
This change is mostly invisible:
31
+
32
+
- previously versions are unable to read/write a new DBs;
33
+
- but the new release is able to handle an old DBs and will silently upgrade ones.
34
+
35
+
Acknowledgements:
36
+
37
+
-[Alex Sharov](https://github.com/AskAlexSharov) for reporting and testing.
38
+
39
+
40
+
## v0.10.5 at 2021-10-13 (obsolete, please use v0.11.1)
41
+
42
+
Unfortunately, the `v0.10.5` accidentally comes not full-compatible with previous releases:
43
+
44
+
-`v0.10.5` can read/processing DBs created by previous releases, i.e. the backward-compatibility is provided;
45
+
- however, previous releases may lead to false-corrupted state with DB that was touched by `v0.10.5`, i.e. the forward-compatibility is broken for `v0.10.4` and earlier.
46
+
47
+
This cannot be fixed, as it requires fixing past versions, which as a result we will just get a current version.
48
+
Therefore, it is recommended to use `v0.11.1` instead of `v0.10.5`.
0 commit comments